Where leaders sit down to talk.

The CIO Table, home

LeadershipThe Long Table

The first 100 days of a new CIO

Listen, decide, show. Whom to meet in the first fortnight, the three conversations that matter most, what not to announce early, and what to tell the board at day 100.

The first 100 days of a new CIO
Photograph: Unsplash

The first 100 days is an arbitrary measure, but a useful one. It is long enough to understand an organisation and short enough that the organisation is still watching closely. A new chief information officer can fail in that period in two opposite ways: by acting before understanding, and so committing to decisions that later have to be unwound, or by understanding without acting, and so becoming part of the furniture before changing anything. Dividing the time into three phases (listen, decide, show) guards against both.

Listen: days 1 to 30

The first fortnight is for reading and meeting, not for opinions. Start with the last two years of board and audit committee papers on technology, which show what the board has been told and what it has been promised. Then the technology budget, comparing plan with actual, and the register of contracts with their renewal and notice dates. Then internal audit reports, any correspondence with regulators, the incident log for the past year and the reviews written afterwards. Finally, the project portfolio, read twice: once as reported, and once after asking the project managers what the status really is.

The meetings should go well beyond direct reports and executive peers. Meet the heads of the largest business units, the head of internal audit, the largest suppliers by spend, and the people who run the service desk, who know better than anyone where things break and how often. Ask everyone the same questions: what works and should be left alone, what should stop, and what a newcomer is most likely to misjudge. Individual answers matter less than the patterns across them.

Three conversations

Three conversations in the first month shape most of what follows.

With the chief financial officer, the aim is a single agreed account of what technology costs. Spending is often scattered across business units, capital and operating budgets, and contracts signed outside the technology function. Agree the baseline before any strategy is written, along with what the CFO believes technology returns and which commitments are already locked into contracts. A strategy built on figures the CFO does not recognise will not survive its first budget round.

With the chief executive, the aim is clarity about why the role was filled and what decisions it carries. Which one or two business outcomes must technology support this year? What can the CIO decide alone? How does the chief executive want to hear bad news, and how much disruption will the business tolerate to fix what is broken?

With the head of security, the aim is to learn what is known but not yet said. Ask which risks are understood but unfunded, which have been formally accepted and by whom, what nearly went wrong in the past year, and whether bad news reaches the board intact. If security reports to the CIO, discuss openly how its independence will be protected.

The listening phase is also the time to choose the early fix: pick one from the complaints heard, so that it can start in the second month and land in the third.

Decide: days 31 to 70

By the second month the patterns are visible, and the temptation is to announce. Resist it. Reorganisations, platform replacements, vendor exits, headcount figures and a branded new strategy all belong after day 100, not before. Early announcements are made on incomplete information and are hard to retract. They put the existing team on the defensive at the moment its knowledge is most needed, and they reach suppliers, who adjust their negotiating positions accordingly.

Decisions should still be made in this phase, but privately: tested with the chief executive and the CFO, costed, and held until they can be presented together with the reasoning behind them.

Show: days 71 to 100

One visible early fix earns the credibility that the larger programme will need. The right candidate is something many staff complain about, which the existing team can fix within weeks, with existing budget and without a new supplier. Slow laptop provisioning for new joiners, unreliable meeting-room video or a cumbersome password reset process are typical. Avoid anything that depends on a vendor change or a large migration, since a delay would turn a quick win into an early failure. Give the credit to the team that delivered it. The fix matters, but so does the signal that good work will be noticed.

The board at day 100

The day-100 report to the board should be short and plain. It should set out what was found, including what the predecessor got right; the three or four priorities for the coming year and the things that will stop to make room for them; the risks the board is currently carrying, with those formally accepted listed separately; what the plan will cost against the baseline agreed with the CFO; and how progress will be reported at each subsequent meeting.

Close the paper with a request for one specific decision rather than a general endorsement: approval to retire a system, to fund a security gap, or to accept a named risk for a stated period. A board that has made a decision about technology within the new CIO’s first 100 days has begun a working relationship. A board that has only noted a presentation has not.