In brief: the first 90 days of a transitional CIO follow three phases of 30 days. First, listen, diagnose, and secure. Then decide and launch an action plan. Finally, deliver the first results and prepare for what comes next. By day 90, management should have a stabilised IT system, a validated roadmap, and clear visibility on the end of the mission.
The essentials
- Before day 1: a half-day framing session with management sets the objectives, mandate, and stakeholders.
- Day 1 to Day 30: listening, assessing the situation, and addressing urgent risks.
- Day 31 to Day 60: decisions, action plan, and first difficult decisions.
- Day 61 to Day 90: first visible results, governance in place, and exit scenario.
- Key to success: explicit support from the leader from day one.
Before day 1: what needs to be framed?
A successful mission partly hinges on what happens before the arrival of the transitional CIO. A framing meeting with the leader should answer five questions:
- Why now? The situation triggering the mission: vacancy, crisis, project in drift, merger.
- What do we expect at the end? Three to five measurable objectives, for example, "ERP started", "successor recruited", or "security plan validated".
- What decision-making power? Budget, contracts, team organisation: what he decides alone and what he submits.
- Who are his interlocutors? The sponsor to management, the business leaders and the key providers.
- How is he presented? A clear announcement from the leader to the teams and providers avoids resistance.
The company also prepares its accesses: contracts, organisational chart, IT budget, existing documentation and necessary accounts.
Days 1 to 30: listen, diagnose, secure
The first month serves to understand quickly, without changing everything, while addressing risks that cannot wait.
What the interim CIO does
- He meets with management, business leaders, the IT team and the main providers, in about twenty interviews.
- He takes inventory of applications, infrastructure, contracts, ongoing projects and the budget.
- He checks the fundamentals of security: backups that are actually restorable, administrator accounts, strong authentication, critical patches.
- He identifies the "fires": contracts that are expiring, projects that are delayed, key personnel leaving.
Deliverable at D+30: a diagnosis of a few pages, with strengths, risks classified by severity and three or four priorities proposed to management.
Signal of success: management finally understands where its IT system stands, in business language.
Days 31 to 60: decide and launch
The second month transforms the diagnosis into decisions. This is often the most delicate phase, as it requires arbitration.
What the interim CIO does
- He gets the priorities and action plan validated by management, with a budget and a timeline.
- He makes the identified difficult decisions: reframe or change a provider, freeze a project, review the scope of an ERP, reorganise the team.
- He establishes governance: a monthly IT committee with management, weekly meetings with providers, and a simple dashboard.
- He launches the first projects, starting with those that reduce the most risks.
Deliverable by D+60: a validated action plan, governance in place, and documented decisions.
Success signal: the teams and providers know who decides, what, and when.
Days 61 to 90: deliver the first results and prepare for the next steps.
The third month must produce visible results and raise the question of what comes next.
What the interim CIO does
- He delivers concrete results: critical risks addressed, project reframed with a new schedule, renegotiated contracts, stabilised team.
- He presents a first report to management: objectives achieved, discrepancies, and adjustments.
- He proposes an exit scenario: recruitment of a salaried CIO, transition to a part-time CIO, or targeted extension of the mission.
- If recruitment is necessary, he writes the job description and initiates the process, as recruitment takes 3 to 6 months.
Deliverable by D+90: a progress report, a 12-month roadmap, and an end-of-mission scenario.
Success signal: management no longer handles urgency and has a clear trajectory.
What traps to avoid, and what is the role of the leader?
Most missions that fail do so for organisational reasons, not lack of skill.
Trap | Consequence | How to avoid it |
|---|---|---|
Vague objectives | Mission that drags on without measurable results | Set 3 to 5 quantified objectives at the framing stage |
Too weak a mandate | Blocked decisions, resistant suppliers | Clearly announce your role and decision-making power |
Change everything from the first month | Loss of team trust, diagnostic errors | Listen for 30 days before structural decisions |
Only deal with the urgent | No trajectory at the end of the mission | Require a roadmap by D+60 |
Forget the exit | Transition that becomes permanent and costly | Plan for handover by D+90 |
The role of the leader consists of three points: publicly support the interim CIO, meet with them at least once a week during the first month, and then quickly make decisions on the trade-offs they present.
Frequently asked questions
Does the process change in the event of a cyberattack?
Yes. The first few days are dedicated to crisis management with technical experts: containment, resumption of activity, communication. The in-depth diagnosis begins once activity is resumed, often after 2 to 4 weeks.
And what if an ERP project is in difficulty?
The diagnosis first focuses on the project: scope, contract, schedule and relationship with the integrator. A decision to "continue, reframe or stop" is generally made before J+45.
How can you tell if the mission is going well?
Check three things: is the diagnosis delivered by J+30, is the plan validated by J+60, and are concrete results visible by J+90? If any of these milestones are missed, hold a reframing meeting.
Can a mission last less than 90 days?
Yes, for a short vacancy or a specific crisis. The same steps then apply in an accelerated manner: diagnosis in one week, decisions in two to three weeks.
What happens after the 90th day?
The mission continues until the objectives are achieved, generally between 6 and 12 months in total, then hands over to a full-time or part-time CIO.
To go further
- Interim CIO: in what cases to call upon one?
- Complete guide: Part-time CIO, the guide for SMEs and mid-sized companies
- What are the missions of an outsourced CIO?
- On Opneo Insights : "Cybersecurity and IT governance: 20 priorities for 2026-2027"
Need an operational CIO quickly? OPNEO offers interim CIOs available within a few days. Chat with us for 30 minutes.
Article written by Aymerick Despres, OPNEO. Updated in November 2026.
note: The process and timelines described are practical benchmarks.