The rhythm: listen, diagnose, decide
A new CIO is judged early, and on a small number of signals: whether you understood the business before talking about technology, whether you kept the lights on, and whether your first decisions were right. The 90 days fall into three blocks of about a month, each closing with a clear output.
| Phase | What you are doing | Output at the end |
|---|---|---|
| Before day one | Agree the mandate, read everything, book the conversations | Draft mandate, first 15 meetings in the calendar |
| Days 1–30 · Listen | Meet people, see operations, gather facts on projects, money and risk | Day-30 readout: what I heard, what I found, what happens next |
| Days 31–60 · Diagnose | Score IT on evidence, decide on projects in flight, form a view of the team | Findings, project decisions, draft priorities |
| Days 61–90 · Decide | Build the roadmap and budget, take people decisions, win approval | Day-90 plan agreed by the executive committee |
Two rules hold across all three phases. Change nothing structural before day 60 unless something is unsafe: early reorganisations are usually built on first impressions. And fix one small, visible irritant in the first month: it shows you listened, at almost no risk.
Fit the plan to the company calendar, not the other way round. If the budget round or a board meeting falls inside your 90 days, move the money and day-90 steps to meet it: missing the cycle can cost a year.
Before day one
Most of the credibility you build in the first month is prepared before you start. Use the weeks between signing and starting.
| Done | Action | Output |
|---|---|---|
| ☐ | Agree with the CEO what success looks like at day 90 and at 12 months. Ask what they would fix first, and what they would not touch. | Notes for the mandate letter |
| ☐ | Clarify your scope and decision rights: reporting line, budget authority, who owns data, security, digital and business applications. | Draft mandate letter |
| ☐ | Read the annual report, strategy, budget, recent board papers, the last internal audit report and the risk register. | Reading notes and first questions |
| ☐ | Ask for the IT pack: organisation chart, budget and actuals, project list, contract list, major incidents of the last 12 months, audit findings. | Document pack |
| ☐ | Build your stakeholder list with HR and the CEO's office; book the first 15 conversations. | Listening tour calendar |
| ☐ | Prepare your day-one message and your first team meeting. | Day-one message and agenda |
Days 1–30: listen
The aim of the first month is to understand how the business makes money, what it expects from technology and what is at risk, in that order. Write down what people say in their own words: you will quote them at day 30.
Week 1
| Done | Action | Output |
|---|---|---|
| ☐ | Meet the whole IT team on day one. Say who you are, how you work and what happens in the next 30 days. Promise to listen before you change anything. | First team meeting held |
| ☐ | Hold a one-to-one with each direct report: their role, priorities, worries, and what they would do in your seat. | One-to-one notes |
| ☐ | Start the listening tour with the CEO, the CFO and the heads of the largest business units. | Listening log |
| ☐ | Walk through operations: service desk, monitoring, change calendar, on-call arrangements. | Operations notes |
| ☐ | Ask security for the top five risks and the state of the incident response plan. Ask when a backup was last restored in a test. | Security briefing note |
Week 2
| Done | Action | Output |
|---|---|---|
| ☐ | Continue the tour: remaining executives, country or site leaders. | Listening log |
| ☐ | Spend a day where the business makes its money: a plant, a store, a branch, a call centre. | Field visit notes |
| ☐ | Review every project in flight with its sponsor: purpose, status, money spent against budget, confidence in the date. | Project list with facts |
| ☐ | Build the cost baseline with finance: what is spent to run, to grow and to transform; people, vendors, licences, cloud. | Cost baseline |
Week 3
| Done | Action | Output |
|---|---|---|
| ☐ | Hold skip-level sessions with IT staff in small groups, and meet the heaviest users in the business. | Listening log |
| ☐ | Start a structured IT health check with your leadership team. Ask for evidence, not opinions. | First scores |
| ☐ | List inherited risks: contracts about to renew, open audit findings, end-of-life systems, people the place cannot run without. Sign nothing material you have not read; ask for short extensions instead. | Inherited risk list |
| ☐ | Collect quick-win candidates and fix one small, visible irritant now. | First quick win |
Week 4
| Done | Action | Output |
|---|---|---|
| ☐ | Meet the top five vendors. Ask what they would change in how you work together, and what the contract does not say. | Vendor notes |
| ☐ | Group what you heard into five themes, in the words people used. | Listening themes |
| ☐ | Give the day-30 readout to the CEO, then to your team: what I heard, what I found, the risks you should hear from me first, and what happens next. | Day-30 readout |
Days 31–60: diagnose
The second month turns impressions into findings. Each finding should have a fact, the evidence behind it, why it matters to the business and a proposed action. Test each one with the person closest to it before it goes in a deck.
| Week | Done | Action | Output |
|---|---|---|---|
| 5 | ☐ | Complete the health check and challenge the scores with two business leaders. | Health check profile |
| 5 | ☐ | Write the findings: fact, evidence, so what, action. | Findings list |
| 5 | ☐ | Form a first view of your leadership team: strengths, gaps, risks. Discuss it with HR only. | Private team assessment |
| 6 | ☐ | Map the business priorities for the next 18 months to what IT must deliver for each. | Priorities to IT implications |
| 6 | ☐ | Choose two or three quick wins, name an owner and a date for each, and tell the people who asked for them. | Quick wins launched |
| 6 | ☐ | Decide on each project in flight: continue, fix, pause or stop. Agree each decision with its sponsor. | Project decisions |
| 7 | ☐ | Go deep on the two weakest areas of the health check. | Deep-dive notes |
| 7 | ☐ | Hold a second conversation with sceptics. Ask what would change their mind. | Updated stakeholder map |
| 7 | ☐ | Set the operating rhythm: leadership meeting, service review, project review, one-to-one with the CEO. | Meeting calendar |
| 8 | ☐ | Draft no more than five 12-month priorities, each tied to a business outcome. | Draft priorities |
| 8 | ☐ | Test the draft with the CEO and CFO: what is missing, what would you drop? | Feedback recorded |
| 8 | ☐ | Draft the target organisation and the two or three people decisions you will have to take. | Organisation options |
Days 61–90: decide
The last month is about commitment: a plan with owners, money and measures, agreed by the people who will hold you to it. Nothing in the day-90 meeting should surprise anyone in the room.
| Week | Done | Action | Output |
|---|---|---|---|
| 9 | ☐ | Build the 12-month roadmap with your team: milestones, owners, dependencies. | Roadmap |
| 9 | ☐ | Size investment and savings with finance. Separate the must-do risk items from the choices. | Budget view |
| 10 | ☐ | Take the people decisions. Tell those affected yourself, with HR, before any announcement. | Decisions communicated |
| 10 | ☐ | Choose five to eight measures you will report every month. | Scorecard |
| 10 | ☐ | Deliver the quick wins and give the credit to the team. | Quick wins closed |
| 11 | ☐ | Walk each executive through the plan one to one before the meeting. | Pre-meeting notes |
| 11 | ☐ | Write the day-90 presentation. Lead with business outcomes, not technology. | Day-90 deck |
| 12 | ☐ | Present to the executive committee and ask for the specific decisions you need. | Decisions minuted |
| 12 | ☐ | Present the plan to the whole IT team: what changes, what does not, and why. | All-hands held |
| 13 | ☐ | Publish the plan on a page and the scorecard; set the date of the first quarterly review. | Plan on a page |
| 13 | ☐ | Thank the people who gave you their time and tell each what you did with what they said. | Thank-you notes |
| 13 | ☐ | Agree your own objectives for the year with the CEO, based on the plan. | Agreed objectives |
Who to meet, and what to ask
Plan for about 40 conversations in the first 30 days, and 50 to 60 by day 60. Meet the people with the most influence first, and go back to sceptics a second time. Five questions work with almost everyone: What does the business need from technology in the next two years? What works well today? What frustrates you most? If you were in my seat, what would you do first? Who else should I talk to?
| Who | When | What you most need to learn |
|---|---|---|
| CEO | Before day one, then every two weeks | Their definition of success, their tolerance for disruption, the two things they would fix first |
| CFO | Week 1 | How IT spend is seen, how investments are approved, what the budget cycle and the cost pressure look like |
| Business unit and function heads | Weeks 1–2 | Their plans for the next two years, where technology helps or blocks them, projects they are waiting for |
| Your direct reports | Week 1, then weekly | What they own, what keeps them awake, what they would change, how they work with each other |
| IT staff, skip-level | Week 3 | What slows work down, what they are proud of, what they think leadership does not see |
| Heavy users in the business | Week 3 | Where the systems get in the way of daily work, and the workarounds they have built |
| Head of internal audit, risk or compliance | Weeks 2–3 | Open findings, regulatory deadlines, where they think IT controls are weakest |
| Top five vendors and partners | Week 4 | How the relationship really works, renewal dates, what they would change |
| Board or audit committee chair | By day 60, if the CEO agrees | What the board worries about in technology, cyber risk in particular |
What to review: the evidence pack
Ask for documents early: how long they take to arrive, and whether they exist at all, tells you something too. The nine areas below are the ones a structured IT health check scores. Score what you find on evidence you have seen, not on what you have been told.
| Area | Ask for | What to look for |
|---|---|---|
| Strategy and alignment | Business strategy, IT strategy if any, last board papers on technology | Whether IT priorities can be traced to business goals |
| Money | IT budget and actuals for two years, run and change split, top 20 contracts | Run share of spend, unexplained growth, renewals in the next 12 months |
| Projects | Project list with budget, spend, dates and sponsor | Too many projects at once, projects with no active sponsor, dates that keep moving |
| Service and operations | Service levels, major incident history, user satisfaction | Repeat incidents, no root-cause reviews, measures nobody outside IT reads |
| Security and resilience | Risk register, last penetration test, incident response plan, backup restore tests, disaster recovery tests | Plans never tested, critical findings left open, no tested recovery for key systems |
| Architecture | Application inventory, end-of-life dates, integration map | Unsupported systems running critical processes, the same data held in several places |
| Data and AI | Data ownership, reporting landscape, AI use and policy | No named data owners, competing versions of key numbers, AI use with no rules |
| People | Organisation chart, headcount and contractors, attrition, open roles, key-person list | Critical knowledge in one or two heads, contractor-heavy teams, long-open roles |
| Governance and risk | Open audit findings, committee terms of reference, decision rights | Decisions escalated by default, committees that review but never decide |
What to decide by day 90
The day-90 meeting is a decision meeting, not an update. Arrive with a short list of specific requests. A plan that asks for nothing commits nobody.
- Five priorities or fewer for the next 12 months, each tied to a business outcome and an owner.
- A decision on every project in flight: continue, fix, pause or stop, agreed with its sponsor.
- The must-do risk items, funded separately from the choices, with dates.
- Your organisation: the structure you will build towards, and the two or three people decisions already taken.
- The money: what the plan costs, what it saves, and what it asks the executive committee to approve now.
- Five to eight measures you will report every month, with today's baseline.
- Your operating rhythm: steering, service and project reviews, and the date of the first quarterly review.
Eight traps that cost new CIOs their credibility
- Reorganising in month one. The structure you inherited has reasons you do not yet see. Wait for the evidence.
- Criticising your predecessor. The people who built what exists are in the room. Describe facts and choices, not blame.
- Talking technology before business. Your first executive presentation should mention outcomes, not platforms.
- Overlooking operations. A major outage in month two will define you more than any plan. Check backups, monitoring and on-call in week one.
- Promising too much. Every early promise becomes a measure. Commit to fewer things and deliver them.
- Hearing only the loud voices. Skip-level sessions and front-line users often see problems executives do not.
- Signing what you inherited. Renewals and large approvals arrive in the first weeks, often with a deadline. Read before you sign, and buy time where you can.
- Surprising people at day 90. Every executive should have seen the plan, and shaped it, before the meeting.
Questions
Does the checklist still apply if I was promoted from inside?
Yes, with two changes. You can shorten the listening tour on the business side, but not with your former peers: the relationship has changed and they will tell you different things now. And run the health check with someone from outside IT, because your own view of what you built is the hardest one to challenge.
What if there is a crisis in my first weeks?
Handle the crisis first and visibly, then resume the plan with the dates moved. A well-run incident early on builds more trust than any presentation. Write down what it taught you about the organisation: it is evidence for the health check.
Should I bring in my own people?
Not before day 60, and only for roles where you have evidence of a gap. Early hires from your previous company send a message to the team you inherited, and it is rarely the one you intend.
How is this different from the CIO First 90 Days Kit?
This page is the checklist. The kit contains the working files: a workbook that tracks the plan, scores the health check and summarises the listening tour, and the day-30 and day-90 presentations with a worked example for one fictional company.