Your First 90 Days as a New Tech Leader

New in seat? What to do on Monday morning, and in each of your first three months, from CIOs who have started new roles many times.

New technology leaders tend to get the same advice: listen, learn, find some quick wins. None of it is wrong. It just doesn't tell you what to do on Monday morning.

We spoke to CIOs who have started new roles many times, across different industries and countries. The detail varied. The pattern didn't. You arrive with a mandate and a honeymoon, and you're handed systems, programmes, budgets, contracts and a team you didn't choose.

The clock is shorter than it looks. Somewhere around month six, you'll be in front of the board explaining an outage, an audit finding, an overspend or a go-live date that someone else signed off. By then it's yours. "I inherited it" works for about a quarter.

So the first 90 days aren't about having all the answers. They're about getting evidence rather than opinions, quickly, across everything you now own.

Monday morning: start the one-page map

Your first job is to see everything you've inherited in one place. Ask for it in week one, and expect it to take a few weeks to fill. It's often the first time anyone has put it all on one page. That alone tells you a lot.

  • The run. Ask for: critical systems, major incidents in the last 12 months, last DR test, open audit and cyber findings. It tells you where the next outage or breach is most likely to come from.
  • The change. Ask for: every major programme, with its annual spend, business sponsor, the outcome it was approved for and its last three status reports. It tells you where most of your budget and reputational risk sits.
  • The money. Ask for: budget against actual, committed spend, next year's plan. It tells you how much room you really have to move.
  • The people. Ask for: your leadership team, key-person dependencies, open roles, attrition. It tells you who the organisation actually runs through.
  • The contracts. Ask for: top suppliers, renewal dates and notice periods for the next 12 months. It tells you which decisions will be made for you if you don't make them first.

Days 1–30: find out what you've actually inherited

The temptation in month one is to fix things. You don't yet know which problems are real and which are just loud. Use the month to fill the map, and to work out where the truth lives.

  • Make sure the lights stay on. Ask what broke in the last year and whether the root cause was fixed, or just the symptom. Ask when disaster recovery was last tested for real. From day one, you're accountable for every open high-risk cyber or audit finding.
  • Find out who the place runs through. Every IT function has three or four people that everything depends on. Know who they are, and what happens if they leave. Don't restructure yet, but start forming a view of who you'd keep.
  • Get the business's version. Ask the CFO and each business head one question: if you could stop one technology programme tomorrow, which would it be? Ask the CEO what success looks like in a year, in their words. Write it down.
  • Check the contract calendar. A renewal or notice period that expires in month two can lock you in for another three years before you've formed a view.

Days 31–60: test what you're being told

Everything you inherited was reported to someone else. Green often means "not yet discussed". Month two is when you stop reading the reports and start testing them.

  • Follow the dates. Line up the last three months of programme reporting. If milestones keep moving right while the status stays amber, the plan isn't a plan.
  • Reconcile the money. Does finance's view of spend match the PMO's? Is each business case still the one that was approved, or has it been quietly rewritten?
  • Ask for the evidence behind the green. Test exit criteria, defect trends, data readiness. If nobody can show you, you have your answer.
  • Compare service reports with the service desk. SLAs can be green while users are furious. Ticket trends and repeat incidents tell you what the dashboard doesn't.
  • Talk to your SI and key suppliers directly. Listen as much for what they avoid as for what they say.

The hard part is that everyone around you has a stake. The people who made the previous decisions often still work for you, and your suppliers have contracts to protect. That isn't bad faith. But the view you're getting is never fully neutral.

By day 60, you should know the two or three things that can hurt you, whether that's a programme, a fragile system, an audit finding or a contract. You should also know the one or two that could make your reputation.

Days 61–90: decide, and set your own agenda

Month three is when you spend the credibility you've built. Your window to change direction without owning the original decision is short, and it closes quietly.

  • Make the programme calls. Put every programme into one of four groups: stop, reset, keep going, or leave alone. A reset at day 80 is a new leader's review. The same reset in month nine is your failure.
  • Make the people calls. The leadership team changes you've been putting off won't get easier. Make the first ones now, while the reason is obviously you arriving rather than something they did.
  • Get into the budget cycle. If your view isn't in next year's numbers, you'll spend a year running your predecessor's plan.
  • Write down your baseline. What you inherited, what you found, and what you're doing about it. Take it to the executive team and the board with evidence, not impressions.

That baseline sets the agenda for your first year. It also protects you when a problem you found in month two finally surfaces in month eight. The 90-day agenda is yours to write. But it's only as good as the evidence underneath it.

Where Performance Radar fits

Most of this you'll do yourself. The programmes are where an independent view pays for itself. They're usually the biggest line in your budget, the hardest to see into, and the area where everyone around you has a stake.

Performance Radar gives new technology leaders an evidence-based view of the programmes they've inherited: where the real risks are, whether the plans, numbers and reporting stand up, and what needs your attention first. Bring us in early and the evidence is in your hands before the hard calls. Bring us in later and it shows whether the calls you've made are holding up. The price is fixed on a one-page scope, and we start within five working days. More on how we work with new technology leaders.

If you've just started a new role, or are about to, schedule a 15-minute introduction.

← All insights

Want an independent read on your own programme?

Fifteen minutes, no obligation and no sales pitch — a straight conversation about whether an independent view would tell you something your reporting isn't.

Book a 15-minute intro