CIO First 100 Days Plan: Week-by-Week Roadmap With Example

11 min read ยท 2026-10-25

A CIO first 100 days plan is a short roadmap that takes a new chief information officer from listening to an approved IT strategy in about 14 weeks. It sets who you meet first, what you assess, which quick wins you deliver and what you present to the CEO and the executive team by day 100. Most solid plans follow the same arc: learn the business, assess IT, fix a few visible problems, then commit to a direction.

The plan below runs in six phases, each with steps and a milestone you can check. It also gives a first-week list, the people to meet in order, a filled-in example, the metrics to report at day 30, 60 and 100, and how to present the plan to the CEO, the board or an interview panel.

Adjust the weight of each phase to your mandate. A CIO hired after a major outage spends more time on stability. A CIO hired to lead a transformation spends more time on strategy and talent.

The roadmap at a glance

Goal: By day 100, the CEO and executive team have approved an IT strategy, a 12 to 18 month roadmap and a target IT organization, and the business has seen three visible improvements. Duration: 14 weeks (100 days)

  1. Prepare and confirm the mandate (Weeks 1-2)

    Agree with the CEO on what success looks like and secure the basics before you change anything.

    • Hold a one-hour mandate meeting with the CEO: the top three business outcomes IT must support, the budget envelope and how you will be judged at day 100.
    • Meet each direct report one to one and ask the same five questions so you can compare answers.
    • Ask the security lead for the incident log, open audit findings and the date of the last tested backup restore.
    • Get the IT budget, the project portfolio list, the org chart and the largest vendor contracts with their renewal dates.
    • Tell the IT team in a short all-hands what you will do in the first 100 days, and what you will not change yet.

    Milestone: A one-page mandate note confirmed by the CEO in writing, listing three outcomes and how each will be measured at day 100.

  2. Listening tour (Weeks 2-5)

    Understand how the business sees IT, from the executive team down to the people who use the systems every day.

    • Meet every executive committee member and ask what IT does well, what slows them down and what they will need in two years.
    • Spend half a day with frontline teams such as customer service, the warehouse or the finance close team, and watch the systems in use.
    • Meet the chair of the audit or risk committee, or the board member closest to technology.
    • Meet the top five vendors by spend and ask what they would change about how you work together.
    • Keep a running pain point log with who raised each issue and how often it came up.

    Milestone: A listening tour summary covering every executive and at least five frontline teams, with the top ten pain points ranked by how often they came up.

  3. Assess the IT estate (Weeks 4-8)

    Build a fact base on cost, risk, projects and people so the strategy rests on data, not opinions.

    • Split the IT budget into running the business and changing it, and list the largest cost lines.
    • Review every active project: sponsor, budget, status, expected value and whether anyone still needs it.
    • Build an application inventory with owner, age, support status and business criticality.
    • Rate security, resilience and data protection against a recognized framework such as NIST CSF, and list the main gaps.
    • Map team skills and key-person dependencies, including systems only one person understands.

    Milestone: An IT assessment pack of about ten slides, reviewed with the CFO, with a red, amber or green rating for cost, risk, delivery and talent.

  4. Quick wins and triage (Weeks 6-10)

    Fix a few problems the business can feel and stop work that no longer earns its place.

    • Pick three quick wins from the pain point log that your team can finish within four weeks without new budget.
    • Pause or stop projects with no active sponsor or no clear value, and move those people to priority work.
    • Close the most urgent security gaps, such as admin accounts without multi-factor authentication or backups never tested.
    • Set up a monthly IT steering meeting where business leaders approve priorities and spending.

    Milestone: Three quick wins delivered and announced, plus a portfolio decision log showing which projects continue, pause or stop.

  5. Strategy and operating model (Weeks 9-13)

    Turn what you learned into a direction the business can fund and the IT team can deliver.

    • Write three to five strategic themes tied to business outcomes, such as a faster order to cash cycle or one customer record.
    • Draft a 12 to 18 month roadmap by quarter, with an owner, dependencies and a rough cost range for each initiative.
    • Design the target IT organization: roles, reporting lines, what stays in-house and what you buy as a service.
    • Test the draft one to one with the CFO, the COO and two business unit heads before any group meeting.

    Milestone: A draft IT strategy and roadmap reviewed by the CFO, with no open objection from any executive committee member.

  6. Present and launch (Weeks 13-14)

    Get formal approval and start delivering against the plan.

    • Present the strategy to the CEO and executive committee with a one-page summary and a short appendix.
    • Share a shorter version with the board or audit committee if the CEO asks for it.
    • Run an IT all-hands to explain the strategy, the new structure and what changes for each team.
    • Publish the roadmap, the steering calendar and the metrics you will report each month.

    Milestone: Executive committee approval recorded in the meeting minutes and the first monthly IT scorecard published.

Shape the plan around your mandate

Not every CIO is hired for the same job. Before you copy any plan, find out which mandate you have. The common ones are: stabilize after outages or a breach, control cost, deliver a major program such as an ERP replacement, or lead a digital transformation. Ask the CEO directly, then check the answer with the CFO.

The mandate changes the weight of each phase. A stabilization mandate pulls risk and operations work into week one and keeps the strategy lighter. A cost mandate puts the budget split and vendor contracts at the center of the assessment. A transformation mandate needs more time with business unit heads and a stronger talent plan. Write the mandate on the first page of your plan so every later choice traces back to it.

Your first-week list

Week one is for access, relationships and safety. Do not announce a reorganization or kill projects yet. People will judge you on how you listen, and you need the facts first.

Keep the list short enough to finish. If an item slips, move it to week two rather than rushing a meeting.

  • Confirm the mandate and day-100 expectations with the CEO.
  • Meet every direct report one to one, about 45 minutes each.
  • Ask for the incident log, open audit findings and the business continuity plan.
  • Get access to the IT budget, the project list and the main vendor contracts.
  • Find out which renewals, audits or go-lives fall inside the next 100 days.
  • Hold a short IT all-hands to introduce yourself and explain how the 100 days will run.
  • Block two hours a week in your calendar for frontline visits.

People to meet, in order

Start with the person who hired you and the people who report to you, then move out to peers, the board and the front line. Use the same questions with every executive so you can compare answers side by side.

Three questions work in almost every meeting: what does IT do well today, what slows you down most, and what will your area need from technology in two years? Add the answers to the pain point log the same day.

  • CEO: mandate, priorities, how decisions get made, who you should never surprise.
  • CFO: IT budget history, capital rules and the business case format finance expects.
  • Direct reports: what works, what is broken, who the strongest people are, what they would do in your seat.
  • COO and business unit heads: the processes that depend on IT and where they lose time.
  • CISO or security lead: incidents, audit findings, top risks and cyber insurance requirements.
  • Audit or risk committee chair: what the board worries about and how they want to hear from IT.
  • Top vendors and frontline users: contract terms, workarounds and the daily friction nobody reports.

Example: a filled-in CIO 100 days plan

Picture a new CIO at a manufacturer with several plants, an aging ERP, finance teams running on spreadsheets and a recent phishing incident. The CEO's mandate: make IT reliable, then bring a plan to replace the ERP. Here is how the six phases could look, with an owner and a milestone for each.

Notice that the ERP decision is not made in the first 100 days. The plan commits to a selection process with a date, which is what the CEO can approve at this stage.

  • Weeks 1-2 (CIO): mandate note agreed with the CEO, all direct reports met, backup restore test scheduled. Milestone: mandate note confirmed.
  • Weeks 2-5 (CIO with plant managers): visits to two plants and the finance close team, all executives met. Milestone: top ten pain points, led by ERP downtime and a slow month-end close.
  • Weeks 4-8 (CIO and IT finance lead): budget split into run and change, project review finds several projects with no active sponsor. Milestone: assessment pack reviewed with the CFO.
  • Weeks 6-10 (infrastructure and security leads): multi-factor authentication on all admin and email accounts, a plant network fix, self-service password reset. Milestone: three quick wins announced, stalled projects paused.
  • Weeks 9-13 (CIO and enterprise architect): four themes: reliable plants, one finance platform, secure by default, plant data people can use. Milestone: CFO review done, ERP selection planned over the next two quarters.
  • Weeks 13-14 (CIO and CEO): executive committee approval, IT all-hands, first monthly scorecard. Milestone: approval in the minutes.

Quick wins that fit a CIO

A good quick win is visible to the business, small enough to finish in a few weeks and possible without new budget. It proves you listened. Pick it from the pain point log, not from your last company.

Avoid quick wins that lock you in, such as signing a new platform contract in month two. That is a strategic decision dressed up as a fast fix.

  • Fix the most common recurring complaint from the listening tour, such as meeting room Wi-Fi or slow laptop delivery for new hires.
  • Turn on multi-factor authentication for every account that still lacks it.
  • Publish a simple IT service catalog with who to contact and expected response times.
  • Stop one or two zombie projects and move the people to priority work.
  • Start the monthly steering meeting so business leaders see priorities and trade-offs.

Metrics to report at day 30, 60 and 100

Report a small, stable set of numbers so the CEO sees a trend, not a new dashboard each month. Take a baseline in the first 30 days, then report the same measures at day 60 and day 100.

Tie each metric to a source the CFO trusts, such as the service desk tool, the finance system or the portfolio decision log. If a number is an estimate, label it as one.

  • Major incidents and downtime of critical systems, from the incident log.
  • Service desk backlog and time to resolve, from the service desk tool.
  • Share of IT spend on running the business versus changing it, from the IT budget.
  • Projects on track, paused or stopped, from the portfolio decision log.
  • Open high-risk security findings, from the risk register.
  • Executive satisfaction with IT, from a five-question survey at day 30 and day 100.

How to present it to the CEO, the board or an interview panel

For the executive committee, lead with one slide: the mandate, what you heard, what you found, three to five themes, the roadmap by quarter and the decisions you need today. Put the assessment detail in an appendix. Leave out technology names unless a decision depends on them.

For the board or audit committee, focus on risk, cost and the timeline of major programs. In an interview, present a lighter version: how you would spend each phase, who you would meet first and how you would know you succeeded. Do not promise a strategy before you have listened. Say you will bring one by day 100, built on what the business tells you.

Common mistakes to avoid

  • Announcing a reorganization in the first month breaks trust before you know the team, so wait until the assessment shows what needs to change.
  • Bringing the strategy from your last company ignores how this business works, so build every theme from the listening tour and the assessment.
  • Spending the 100 days mostly with IT people leaves you without business allies, so hold at least half of your meetings outside IT.
  • Skipping the security and backup check in week one leaves you owning an inherited incident, so ask for the incident log and a tested restore right away.
  • Choosing quick wins that need new budget turns them into slow wins, so pick fixes your team can deliver with what it has.
  • Showing the strategy for the first time in the executive meeting invites surprise objections, so test it one to one with the CFO and key executives first.

Frequently asked questions

What should a CIO do in the first 100 days?

Confirm the mandate with the CEO, meet every executive and direct report, and assess cost, risk, projects and talent. Deliver two or three visible quick wins along the way. By day 100, present an IT strategy and roadmap for approval.

How do I present a 100 day plan in a CIO interview?

Show the phases on one slide: listen, assess, quick wins, strategy, present. Name the people you would meet first and the metrics you would report. Make clear that the strategy comes from what you learn, not from a plan you bring with you.

What are good quick wins for a new CIO?

Pick fixes the business can see and your team can finish in a few weeks without new budget. Common examples are closing multi-factor authentication gaps, fixing a recurring complaint, publishing a service catalog and stopping projects with no sponsor.

When should a new CIO change the IT organization?

Usually after the assessment, once you know the team's skills and the strategy it must deliver. Announcing structure changes in the first weeks tends to freeze the team. A common approach is to present the target organization with the strategy around day 100.

Is a CIO 100 day plan the same as an IT strategy?

No. The 100 day plan is how you get to the strategy: who you meet, what you assess and what you fix first. The IT strategy is the output, a set of themes and a multi-quarter roadmap the business approves and funds.

Generate this roadmap with AI