An interim CIO is called in when the business cannot wait. The head of IT has left with no successor, a critical migration is going off the rails, a cyberattack has brought activity to a halt, an acquisition requires two systems to be merged within months. In these situations the business needs someone experienced, available at once, able to decide from the first week — and who will leave once the problem is solved.
The last part of that sentence matters most. An interim CIO is a particular form of interim management: the assignment has an announced end, and that end is what defines its content. Without it, interim becomes a temporary presence that lingers, at the price of a permanent emergency.
Situations that call for an interim CIO
Four situations come up again and again, and what they share is that they leave neither time to recruit nor the option of waiting.
- An unplanned departure. The CIO leaves, sometimes abruptly. Hiring will take months; meanwhile suppliers, projects and incidents do not wait.
- A project in trouble. An ERP migration, a change of hosting provider, a roll-out running over budget and schedule. Someone from outside is needed to settle what the existing team can no longer settle.
- A crisis. A cyberattack, a major outage, a failing supplier. The priority is to restore, then understand, then rebuild — in that order.
- A one-off transformation. An acquisition, a merger, a reorganisation that requires the information system to be overhauled in depth, over a short period.
A fifth situation looks like the others but is not one: using interim to postpone a decision. The business has not settled between hiring a CIO, outsourcing the function or dropping it, so it installs an interim in the meantime. The assignment then has neither an exit objective nor an end date. It becomes a temporary fix that lasts, at the price of an emergency that is not one.
In each case the need is intense and temporary. That is what sets interim apart from other forms of support, and what should guide the choice.
Interim and part-time: two different logics
The two arrangements are often presented together, because they draw on similar profiles. Yet they answer two opposite needs.
| Criterion | Interim CIO | Part-time CIO |
|---|---|---|
| Need | Intense, urgent, temporary | Regular, lasting |
| Presence | Often full time | A few days a month |
| Duration | A few months, with an announced end | Open-ended, reviewed periodically |
| Objective | Resolve a situation and hand over | Install a steering function |
The choice is therefore made on the nature of the need, not the profile. A business that has lost its CIO and will hire another needs an interim. A business that has never had a CIO and will not have one full time needs a part-time CIO.
Sometimes one follows the other. An interim can reveal that the business does not need a full-time CIO, and end with a part-time arrangement being set up. The reverse is also true: a part-time CIO who sees decisions becoming daily prepares a hire.
Getting the first 30 days right
An interim CIO has no time for an observation period. The first month establishes legitimacy with management, teams and suppliers. It falls into three stages.
- Stabilise. Identify what could break in the coming days — access held by a single person, unverified backups, contracts about to expire — and secure it before anything else.
- Diagnose. Meet the teams and suppliers, read the contracts, rebuild the map of what exists. The aim is not completeness: it is to know where the real risks lie.
- Decide. Take a few visible, explained decisions, and stick to them. An interim who decides nothing for a month loses the trust they came to restore.
Communication matters as much as decisions. Internal teams want to know what changes for them; suppliers want to know who decides from now on; management wants to know where things stand. A clear message to each, in the first week, prevents the arrival of an outsider being read as a sanction or as a caretaker without authority. An interim CIO needs an explicit mandate, announced by management itself: without it, suppliers will wait for the successor before committing.
At the end of that first month, management should have a short note: the state of play, the risks identified, the decisions taken, and the plan through to the exit. That document is what turns the interim into an assignment that can be steered rather than an emergency presence.
Preparing the exit from day one
A successful interim is recognised by what it leaves behind. The exit is prepared from day one, and it takes one of three forms:
- a successor hired, with a job description written from what the interim has learned, and an overlap period;
- a project delivered, handed to a team able to run it, with the necessary documentation;
- a lasting steering arrangement in place — part-time leadership, written governance, suppliers refocused — when the business does not need a full-time CIO.
These forms of exit are written into the engagement letter, before arrival. It sets out the objective, the expected duration, the deliverables, the reporting line — the managing director, never a supplier — and the criteria by which the assignment will be recognised as complete. An engagement letter that does not say how the interim ends prepares an interim that does not end.
The profile is chosen accordingly. A good interim CIO has already been through comparable situations, can decide without having all the information, and has no stake in the choice of suppliers they will have to arbitrate. That last condition should be checked: someone paid by a software vendor or an integrator cannot freely decide between them.
In every case the interim must leave a written record: the map, the decision log, the state of contracts, the roadmap. When the business then has to plan over several years, that material becomes the basis for an IT master plan. It is also what allows Maeliom Consulting to commit to an end date: what is written down can be taken over.
Common questions
How long does an interim CIO assignment last?
Long enough to resolve the situation that prompted it and to hand over: often a few months. The duration is set at the outset from the exit objective, and revised if the situation demands it, not out of habit.
What is the difference between an interim CIO and an interim manager?
An interim CIO is an interim manager specialising in information systems. The logic is the same — a bounded assignment, an exit objective — but the scope is that of an IT department.
Can an interim CIO become a part-time CIO?
Yes, when the interim shows that the business does not need a full-time CIO. The switch should then be decided explicitly, with a new engagement framework, rather than letting the interim drag on.