The 90-Day CTO: What a New Technology Leader Should Assess, Decide, and Deliver

You have just been hired as CTO. The board expects transformation. The team expects stability. Your peers expect collaboration. And you have 90 days before everyone forms an opinion about whether you were the right hire.

This post provides a structured approach to the first 90 days — what to assess, what to decide, and what to deliver. It is based on patterns we have observed across CTOs who succeeded and those who did not.

The 90-Day Framework

Loading diagram...

Days 1-30: Listen and Assess

The single most important rule: do not make structural decisions in the first 30 days. You do not have enough context, and early decisions based on incomplete information erode trust with the team.

Loading diagram...

Week 1: People Mapping

Meet every direct report one-on-one. Ask:

• What is working well that I should not change?
• What is the biggest obstacle to your team's productivity?
• If you had one wish for the technology organisation, what would it be?
• What should I know that nobody will volunteer?

Meet your peer executives. Ask:

• What does technology do well for your department?
• Where does technology create friction?
• What do you need from the technology organisation in the next 12 months?

Meet the CEO/board sponsor. Ask:

• What does success look like for me in 12 months?
• What was the trigger for this hire?
• What was the previous technology leader's biggest gap?

Week 2: Architecture Assessment

You do not need to understand every system in detail. You need to understand:

1. The critical path — Which systems generate revenue? Which systems, if they fail, stop the business?
2. The architecture age — How old is the core platform? When was the last significant modernisation?
3. The integration landscape — How do systems communicate? Is it a well-designed integration layer or point-to-point spaghetti?
4. The technical debt — What does the team consider the biggest technical liability?
5. The security posture — When was the last penetration test? What were the findings? Were they remediated?

Week 3: Operational Health

Review the last 12 months of:

• Incidents — Frequency, severity, resolution time, root causes. Recurring incidents in the same systems indicate systemic problems.
• Deployments — Frequency, failure rate, rollback frequency. Low deployment frequency suggests high release risk.
• Team metrics — Attrition rate, open positions, time-to-fill. High attrition in specific teams signals management or technology problems.
• Vendor spend — Top 10 vendors, contract terms, upcoming renewals. Are there renegotiation opportunities?

Week 4: Synthesis

Create your assessment document — a private document for your own clarity:

Strengths: What is genuinely good about the technology organisation? Risks: What could cause a significant business impact in the next 6 months? Gaps: Where is the organisation underinvesting? Opportunities: Where can technology create business value that is not being captured?

Days 31-60: Prioritise and Plan

Identify 3 Quick Wins

Quick wins build credibility. Choose actions that:

• Are visible to stakeholders outside technology
• Can be delivered within 30 days
• Do not require reorganisation or significant budget
• Address a pain point you heard repeatedly in Week 1

Examples:

• Fix the deployment pipeline that has been failing 30% of the time
• Implement MFA for the executive team (addresses a security gap the board cares about)
• Automate the monthly reporting process that consumes 3 days of analyst time
• Resolve the long-standing integration bug between CRM and billing

Define 3 Strategic Priorities

Based on your assessment, identify the three most important investments for the next 12 months. For each:

1. The problem — In business terms, not technical terms
2. The proposed approach — High-level, not detailed
3. The expected outcome — Measurable business impact
4. The investment required — Team, budget, timeline
5. The risk of inaction — What happens if we do nothing?

Make One Team Decision

By day 45, you should understand team dynamics well enough to make one structural decision. This might be:

• Hiring a key role that is clearly missing (e.g., security lead, platform architect)
• Reassigning a team lead who is in the wrong role
• Creating a new team to address a capability gap
• Merging two teams that should not be separate

Make one decision, execute it well, and observe the effect before making more.

Days 61-90: Execute and Communicate

Deliver the Quick Wins

At least two of your three quick wins should be complete by day 75. Communicate the results broadly — not as self-promotion, but as evidence that the technology organisation is improving.

Prepare Your First Board Presentation

The day 90 board presentation is your defining moment. Structure it as:

Slide 1: Current State Assessment (2 minutes)

• Technology strengths (start positive)
• Key risks and gaps (honest but not alarming)
• How this compares to industry benchmarks

Slide 2: Strategic Priorities (3 minutes)

• Three priorities with business impact, not technical detail
• Expected outcomes with timelines
• Investment required

Slide 3: Quick Wins Delivered (1 minute)

• What was accomplished in the first 90 days
• Business impact of each win

Slide 4: 12-Month Roadmap (2 minutes)

• Quarterly milestones
• Resource plan
• Key decision points for the board

Slide 5: What I Need (1 minute)

• Budget approval for strategic priorities
• Board support for organisational changes
• Specific decisions you need from the board

Establish Your Operating Rhythm

By day 90, you should have established:

• Weekly 1:1s with direct reports
• Bi-weekly architecture review
• Monthly technology leadership meeting
• Quarterly business review with peer executives
• Regular informal conversations with engineers (not just managers)

Common First-90-Day Mistakes

Mistake 1: Reorganising Before Understanding

Resist the urge to restructure. Understand why the current structure exists before changing it. Some seemingly irrational structures exist for good reasons.

Mistake 2: Bringing Your Old Playbook

What worked at your previous company may not work here. Different company, different culture, different constraints. Adapt your approach to the context.

Mistake 3: Promising Before Assessing

Do not commit to timelines or outcomes before completing your assessment. Early promises create expectations that constrain your options later.

Mistake 4: Focusing Only on Technology

Your job is to make the business successful through technology, not to build the best technology for its own sake. Every decision should connect to a business outcome.

Mistake 5: Ignoring the Team's History

The team has been through things you do not know about — failed projects, broken promises from previous leadership, painful reorganisations. Acknowledge this history and earn trust through consistent behaviour.

---

Starting a new CTO role and want an experienced assessment partner? Contact us — we help new technology leaders build their 90-day assessment and strategic plan.