How should a new CTO approach their first 90 days?

Question

Accepted Answer

The first 90 days are about **learning before acting**. A new CTO should diagnose the situation, build relationships, and earn trust before making major changes.

## A simple framework

```text
DAYS 0-30  → LISTEN & LEARN
  - Meet engineers, leaders, peers, the CEO, key customers
  - Understand the architecture, the roadmap, the pain points
  - Identify what is working (preserve it) vs broken

DAYS 30-60 → DIAGNOSE & PRIORITIZE
  - Form a clear view of the top 3-5 problems
  - Validate it with the team and the CEO

DAYS 60-90 → ACT ON QUICK WINS + SHARE A PLAN
  - Deliver one or two visible early wins
  - Communicate a 6-12 month direction
```

## Concrete example

A new CTO spends weeks one to four in one-on-ones, discovers that releases take three weeks and morale is low, and by day 90 has shipped a faster CI pipeline (a quick win) while presenting a plan to restructure teams around clearer ownership.

## Trade-offs and pitfalls

- **Pitfall:** arriving with a fixed plan and changing things before understanding context.
- **Pitfall:** listening forever and never acting, which erodes confidence.

## Why it matters

First impressions set the tone for a leader's entire tenure.

A disciplined entry builds the trust and context needed to lead change later.

Moving too fast burns credibility; moving too slow signals weakness.

The balance is the skill.