Leadership · Playbook
The CIO’s first 100 days: listen, diagnose, commit.
A practical first-100-days plan for new CIOs: what to learn in days 1-30, what to diagnose in days 31-60, what to commit to by day 100, the five questions to ask every executive, and the pitfalls to avoid.
A new CIO’s first 100 days run in three phases. Days 1-30: listen and stabilize. Map stakeholders, confirm expectations and check for fires. Days 31-60: diagnose portfolio, money, people, architecture and risk. Days 61-100: commit to a one-page direction, two or three visible quick wins and an operating rhythm with the executive team.
The principle behind the first 100 days
A new CIO’s first 100 days should build credibility before changing direction: learn the business, diagnose the technology estate, secure a few visible wins, then commit to a direction the executive team already expects. Speed matters, but premature reorganizations and platform announcements are the most common way new CIOs lose trust.
Days 1-30: listen and stabilize
The first 30 days are for building a stakeholder map, understanding what the business expects from IT, and making sure nothing is on fire.
- Meet every executive-team member and ask the same five questions (below), so their answers are comparable.
- Get briefed on live incidents, at-risk programs, audit findings and contract renewals due within 12 months.
- Meet your direct reports one-to-one, then a sample of front-line engineers and service-desk staff.
- Write down the three outcomes the CEO expects from you, and confirm them.
Days 31-60: diagnose the estate
Days 31 to 60 turn impressions into evidence across five areas: portfolio, money, people, architecture and risk.
| Area | What to establish |
|---|---|
| Portfolio | Every major program: sponsor, status, value case, and whether it should continue |
| Money | Run vs change spend, top vendors, cloud cost trend, commitments you inherit |
| People | Leadership bench, critical single points of knowledge, skills gaps, morale |
| Architecture | Core systems, technical debt hot spots, integration fragility, data quality |
| Risk | Cyber resilience posture, proven RTO/RPO, third-party concentration, shadow AI |
Days 61-100: commit to a direction
By day 100, a new CIO should publish a one-page direction, deliver two or three visible quick wins, and install an operating rhythm with the executive team.
- Strategy on a page: three outcomes, the programs that serve them, and what you will stop doing.
- Quick wins: fixes that the business feels and that matter to the people who hired you, such as a painful approval flow, a chronic outage or a slow onboarding process.
- Operating rhythm: a monthly technology review with the executive team and a quarterly board update format.
- Your team: make leadership changes you are confident about, and signal the rest as a timeline.
Five questions to ask every executive
- What does IT do today that you would miss most if it stopped?
- What is the one thing you wish IT would do that it doesn’t?
- Which decision in the next 12 months depends most on technology?
- Where have you been let down before, and why?
- How will you judge whether I have succeeded a year from now?
Common first-100-day pitfalls
- Reorganizing before diagnosing. Structure changes are expensive to reverse and often solve the wrong problem.
- Criticizing your predecessor. The people who made those decisions still work there.
- Announcing a platform before a problem. Lead with the outcome the business wants, not the technology.
- Going it alone. A peer who has done this recently is the fastest shortcut available. That is what the First-100-Days Table is for.
Frequently asked questions
What should a new CIO do in the first week?
Meet the CEO, CFO and your direct reports. Confirm the top three expectations for the role in writing. Get briefed on any live incident or at-risk program. Don’t announce changes yet.
When should a new CIO present a strategy?
Around day 90 to 100, as a one page that has been pre-tested privately with the CEO, CFO and two or three business leaders, so there are no surprises in the room.
This playbook is a synthesis for discussion, not legal or regulatory advice. Confirm obligations with counsel. Spotted something out of date? Tell the editors.