At some point, technology decisions outgrow the people making them. The ERP is showing its age, security questions are getting harder, vendors call the owner directly and the IT manager, who is excellent at keeping things running, isn't at the table when the big decisions are made.
The reflex is to ask who to hire. The better question is what you actually need: a decision on one specific question, steady leadership over time or a full-time leader with a team to run. Each answer points to a different model. Athletes know the pattern: a session with a specialist to fix one problem, a coach who plans the season or a full-time staff once the program justifies it.
A disclosure before going further: I offer two of these three models, so weigh my view accordingly. Sometimes the honest answer is the third.
Three different needs
A consultant, on a mandate, fits a question with an end. Choosing a system. Building a roadmap. Assessing a project that's going sideways. The work has a scope, a duration and deliverables, and when it's done, it's done.
A fractional CIO fits a need that's ongoing but not full-time. This person owns the technology roadmap and budget, manages vendors, directs the IT team or the managed service provider and sits with management at a regular rhythm. They're part of how the company runs, just not every day.
A full-time CIO fits a company where technology is a daily leadership job: a team to lead, several projects running at once, a budget that needs constant attention and decisions that can't wait for the next scheduled visit.
The decision rule
Ask two questions.
- Does the need end? If yes, a mandate. If no, go to the second question.
- Is there a full-time leadership job's worth of work every week, with a team to lead? If yes, hire. If no, a fractional CIO.
Most of the difficulty lies in answering the second question honestly. Companies tend to overestimate the need when they're anxious and underestimate it when they're busy.
Signs you need each one
A mandate, when:
- one decision or project is on the table, with a natural end
- you need an outside view to settle an internal debate
- the work requires expertise you won't need again for years
A fractional CIO, when:
- technology decisions keep coming, not just one
- nobody at the management table owns technology
- vendors and contracts are handled by whoever happens to be available
- you have IT staff or a managed service provider, but no one setting their direction
A full-time hire, when:
- several significant projects run at the same time, all year
- the internal team is large enough to need daily leadership
- technology is part of how you compete, not just how you operate
- you're ready to give that person real authority and a seat at the table
Three common mistakes
Hiring a full-time CIO too early. Without a team, a budget or authority, a senior hire ends up as an expensive IT manager, or leaves. Either way, the company concludes that "the CIO role didn't work", when the timing was the problem.
Hiring an IT manager and expecting a CIO. Keeping systems running and setting technology direction are two different jobs. Ask one person to do both, and the urgent usually wins over the important.
Using consultants for an ongoing need. A string of mandates to cover what is really a permanent responsibility creates dependency without accountability. If you keep calling the same advisor for the same kind of decision, the need isn't a project any more.
What to ask, whatever the model
Once you know which model fits, the conversation with candidates is easier to structure. A few questions apply to all three:
- Scope. What exactly will this person own, and what stays with management?
- Authority. Can they decide on vendors, budget and priorities, or only recommend?
- Rhythm. How often will they meet with management, and what will they report?
- First weeks. What will you have in hand early, before the larger work is done?
- Exit. How does the arrangement end, and what does your team keep when it does?
The answers matter as much as the model. A fractional CIO with no authority, or a full-time hire with no clear scope, ends up in the same place: a title without a job.
Often a sequence, not a choice
These models often follow one another. A mandate clarifies where the company stands and what it needs. A fractional CIO then carries the plan forward, builds the team and the habits and makes it clear whether a full-time role is justified, or not yet. When the time comes, a fractional CIO is also well placed to define the role and help assess candidates.
Where to start
Put the two questions to your management team and answer them in writing. If the answer still isn't clear, a 30-minute call is a reasonable next step.