- 1 The first 90 days should produce clarity, trust, and accurate diagnosis — not comprehensive deliverables
- 2 The instinct to move quickly and show visible progress is often destructive in the first phase
- 3 Credibility in technical leadership is built through reliability and judgement, not strategy documents
There is a version of the first-90-days CTO narrative that is widely circulated and largely unhelpful.
In this version, the new CTO arrives, spends a few weeks assessing the situation, then presents a comprehensive technology strategy, an updated architecture vision, an engineering team restructuring plan, and a vendor consolidation roadmap. All of this is done within the first quarter, signalling to the business that the hire was justified and that change is coming.
Businesses that expect this tend to be disappointed by the reality of a strong early-phase CTO. And businesses where CTOs deliver this version of the first 90 days often create significant downstream problems from decisions made too quickly, on insufficient information, without the organisational relationships required to make them stick.
The evidence for what actually produces durable value in CTO tenures points in a different direction.
The most important early asset is an accurate picture
The single most valuable output of the first 90 days is an accurate, unvarnished view of the current state — of the technology estate, the engineering capability, the vendor landscape, the decision-making culture, and the gap between how the organisation describes its technical situation and how that situation actually is.
This sounds obvious. In practice, it requires significant resistance to the social and professional pressure to form confident views quickly.
When a CTO joins, they receive information from multiple sources with multiple agendas. Technology teams present their situation with some degree of advocacy — emphasising the challenges they face, the constraints they operate under, the quality of their work. Stakeholders describe problems in terms that are shaped by their departmental interests. Vendors present their own services favourably. The formal documentation often reflects how things were meant to work rather than how they work in practice.
Arriving at an accurate picture requires triangulating across these sources, asking questions that test the consistency of what is being said, and spending time where the actual work happens rather than only in management conversations.
ONS management practices research consistently finds that the quality of information available to decision-makers is one of the strongest predictors of management quality. In technical leadership specifically, the quality of the early diagnosis shapes the quality of every decision that follows. An inaccurate picture in month one produces misaligned priorities in months two through twelve.
Listening is an active discipline, not a passive one
The most effective early-phase CTO engagements involve structured, intentional listening — conversations designed to surface specific things, not general conversations about how things are going.
The questions that produce the most useful information are usually not the obvious ones. Not “what are the main technology challenges?” — which produces rehearsed answers — but “tell me about a technology decision in the last 12 months that you would make differently now, and why” or “where do you spend time in this organisation that you think is avoidable?” or “what does this business not understand about its technology situation that it should?”
These questions produce answers that reveal patterns: where decisions are made without adequate information, where accountability is unclear, where the organisation’s understanding of its own technology situation is significantly optimistic, where the real constraints sit that do not appear in any formal document.
Establishing decision clarity early
One of the highest-value early interventions is establishing explicit clarity about decision rights in the technology function.
In most organisations that have operated without senior technical leadership — or with technical leadership that was not fully effective — decision-making has drifted. Some decisions are being made by people who are uncertain whether they should be making them. Others are being made by nobody. Others are being made by multiple people independently, producing inconsistent outcomes.
Making the decision rights explicit — who decides what, what information they need to decide it, how escalation works, what the criteria are for different categories of decision — removes a significant source of operational friction. It also creates the accountability structures that make subsequent governance improvements possible.
This does not require a comprehensive governance framework. In the first 90 days, it usually means a small number of explicit conversations about the most consequential decisions, and clarity about how they will be handled going forward.
What the first deliverable should actually be
The most useful formal output of the first 90 days is not a strategy document. It is a clear, honest, prioritised view of the situation: what the organisation has, what is working and what is not, where the highest-value opportunities lie, what the two or three most important changes are, and what the conditions are that would allow those changes to be made effectively.
That output is valuable not because it is comprehensive but because it is accurate and prioritised. It gives the business something it can act on — not a vision to aspire to, but a set of decisions to make.
It is also the foundation on which a credible longer-term plan is built. A 12-month technology strategy produced without the foundation of an accurate 90-day diagnosis is a document written from insufficient information. The businesses that have implemented their technology strategies most effectively are almost always the ones that invested in the diagnostic phase before committing to direction.
Building credibility through reliability, not performance
Credibility in technical leadership is not built through impressive presentations or ambitious strategy. It is built through consistency: making sound judgements, following through on commitments, being honest when something is unclear, and demonstrating over time that decisions reflect actual understanding rather than confident-sounding guesswork.
In the first 90 days, this means being selective about what is committed to. It means being explicit about what additional information is needed before forming a definitive view. It means communicating clearly and consistently with the teams that will be most affected by technology decisions. And it means resisting the performance of confidence in situations where genuine confidence is not yet warranted.
The organisations where new CTOs create the most lasting value are almost always the ones that created the conditions for an honest, well-informed early phase. The ones where the first 90 days became a performance rather than a diagnosis typically take longer to recover from the decisions made in that period than if the CTO had started more slowly.
Relevant service CTA: CTO as a Service — experienced technology leadership that starts with an accurate picture and builds on it.
Related posts: Do You Actually Need a CTO Yet? | What to Look for in a Fractional CTO | Fractional CTO vs Full-Time CTO
Sources