Promote the strongest operator and wait for strategy
The title changes, the work does not, and a year later the roadmap is still a list of systems. The person is now failing at a job nobody defined, having been excellent at one that was.
The comparison
Fractional CIO vs IT director
These are commonly treated as the same job at two salary levels. They are different jobs, and the confusion costs good people their careers.
The actual difference
One makes the estate work. The other decides what it should be
An IT director is accountable for delivery: the systems run, the tickets close, the projects land, the team functions. It is a demanding job and a company without somebody doing it well is in trouble quickly.
A CIO is accountable for direction: where the technology is going, what it costs against what it returns, what could stop the business, and which of those things gets attention first. The output is not a working estate, it is a set of decisions the business has agreed to and can be held to.
These are adjacent, and they are not a ladder. The most common failure is a company promoting an excellent director into a CIO title on the assumption that the second job is the first job with more scope. It is not. The skills that make somebody outstanding at delivery, bias to action, deep operational knowledge, willingness to own the detail, are the same ones that make it hard to spend a quarter on a budget argument with the board. Strategy does not appear, everyone is disappointed, and a good operator ends up carrying the blame for a structural mistake.
The second failure is quieter. A company hires a director and expects a roadmap, and the director produces a competent plan for the estate they own. It is a technology plan rather than a business one, because they were never given the business context, the budget authority or the board access that would make it otherwise. Nobody did anything wrong, and the plan still does not answer the question the board asked.
In practice these roles are complements far more often than alternatives. A director with a clear direction and somebody senior to escalate to performs markedly better, because most of what frustrates a good operator is ambiguity above them rather than work in front of them.
The fork
Two ways this usually goes
Keep them running it, add the altitude above
The director keeps delivery, which is where they are strong, and a fractional CIO owns direction, budget and the board conversation. Delivery usually improves, because the ambiguity above them goes away.
Side by side
Fractional CIO and IT director, on the axes that separate them
| Fractional CIO | IT director | |
|---|---|---|
| Accountable for | The roadmap, the budget and the risk register | Delivery, operations and the team |
| The question they answer | What should we be doing, and what will it cost | Is it working, and when will it be done |
| Where they sit | In the board conversation, in business language | In the operation, close to the work |
| Vendor relationships | Selection, negotiation and holding to account | Day-to-day management and escalation |
| Experience of your next size | Has run technology at a larger company | Often has not, through no fault of their own |
| Presence | A defined cadence, not there daily | Full time, which is what delivery requires |
Which one you need
How to tell them apart
You need the altitude when
- The board is asking questions your strongest technologist cannot answer in business terms
- Technology spend is growing and nobody can say what it returns
- A decision is coming that is bigger than anything the current team has made before
- Delivery is fine and the direction is the thing nobody owns
- You are about to promote somebody into a CIO title and want to know whether that is the right move
You need a director, not a CIO, when
- The problem is execution: things are not getting done, or not getting done well
- There is a team to manage day to day, and nobody managing it
- The direction is already clear and agreed, and what is missing is delivery against it
- The estate needs somebody who owns the detail and is there when it breaks
Questions
What people ask about this choice
Can our IT director just step up into the CIO role?
Sometimes, and it is worth being deliberate rather than hopeful about it. The two roles need different things: one is accountable for delivery, the other for direction, budget and the board conversation. Some directors have the appetite and the commercial instinct for that and grow into it well. Many are excellent at the job they already have and are set up to fail by a title change that comes without a defined mandate.
Will a fractional CIO undermine our IT director?
It should do the opposite, and if it does not, something has been set up wrong. The director keeps delivery, which is their job and usually their strength. What changes is that priorities become clear, escalation has somewhere to go, and the case for budget gets made by somebody whose job is to make it. Most good directors find that a relief rather than a threat.
Do we need both?
Often, yes, and that is the normal arrangement rather than a luxury. Direction without delivery is a document, and delivery without direction is motion. What varies is whether the direction role needs to be full time, which for most companies between roughly 50 and 500 people it does not.
What if we have neither?
Then delivery is the first problem to solve, because advice needs somebody able to act on it. A fractional CIO can set direction and hold a provider to account, but the role advises rather than executes. Where there is no internal owner at all, the honest sequence is to get execution capability in place, whether that is a hire or a managed service, and add the direction above it.
Not sure which one you need?
That is a reasonable place to be, and it is usually answerable in a conversation rather than a proposal. Start with a thirty-minute call.
The other comparisons