- Key Takeaways: The New CTO's First 90 Days
- Before Day One: The Preparation Phase
- Days 1-30: Listen and Diagnose
- Days 31-60: Align and Decide
- Days 61-90: Act and Deliver
- The 90-Day Milestone Summary
- The Early Win: Choosing It Deliberately
- The Onboarding Mistake That Sinks New CTOs
- What the Organization Owes the Transition
- From 90 Days to the Full Tenure
- Frequently Asked Questions
As Global Head of Research & Leadership Advisory at JRG Partners, I wrote this first-90-days roadmap for a new CTO because transitions are where hiring investments are protected or squandered. The structure below, listen and diagnose, align and decide, act and deliver, is the pattern behind the successful transitions we have observed, adapted to this role’s specific terrain.
Key Takeaways: The New CTO’s First 90 Days
- The 90-day arc runs listen-diagnose (days 1-30), align-decide (31-60), act-deliver (61-90); executives who invert the order pay for it all tenure.
- Early wins are chosen, not stumbled upon: one visible, meaningful, fast result in the first two months buys the license for the slower structural work.
- Fixing the one recurring incident class that had burned the team quarterly earns the engineering organization’s belief.
- The receiving organization owns half the transition: mandate clarity, stakeholder introductions, and air cover are the employer’s deliverables.
- New CTOs are tempted to announce grand re-platforming early; rewrites declared before trust is earned unite the organization against them.
Before Day One: The Preparation Phase
Treat the pre-start window as phase zero: documents read, mandate written, stakeholder map drafted, and the first-week calendar built around listening rather than being presented to. The single highest-leverage artifact is a one-page mandate agreed with your manager before you start, because every later disagreement will be settled by whether it exists.
Days 1-30: Listen and Diagnose
Month one exists to establish truth: baseline, team, and terrain. The CTO-specific diagnostic list:
- Read the architecture through its artifacts: incident history, deploy pipelines, and the debt register nobody maintains
- Meet every senior engineer and listen for what they would fix first
- Assess delivery reality: commitments versus shipments over the last four quarters
- Review security posture and the last three incidents or near-misses
- Understand the product roadmap’s technical feasibility honestly
The discipline is restraint: diagnoses shared as hypotheses invite correction while it is cheap, and the organization notices who listens before deciding.
Days 31-60: Align and Decide
Month two turns the picture into a plan, agreed with the people who must fund and defend it:
- Deliver the technical assessment: platform risks, delivery capability, team, and the sequenced plan
- Make the architecture calls that unblock everything else, and document the trade-offs
- Address the leadership or organization design gaps surfaced
- Set the AI strategy at practical altitude: what ships this year, what is research, what is noise
Days 61-90: Act and Deliver
The third month is for visible motion: the plan launched, the rhythm installed, and the first win banked:
- Ship the first visible commitment on time, the delivery culture reset in miniature
- Stabilize the worst reliability or security exposure with the fix verified
- Publish the technical roadmap in business language the board can govern
- Install the engineering metrics and review rhythm as system health, not surveillance
The 90-Day Milestone Summary
| Phase | Focus | Exit Artifact |
|---|---|---|
| Before day one | Mandate, materials, stakeholder map | Written mandate agreed with the hiring leader |
| Days 1-30 | Listening tour, baseline truth, team assessment | The honest diagnosis, delivered upward |
| Days 31-60 | Direction set, urgent people decisions, operating rhythm designed | The plan agreed, with resources and dates |
| Days 61-90 | Visible execution, first win, scorecard live | The early win delivered; the go-forward KPIs published |
The Early Win: Choosing It Deliberately
Early wins are selected for three properties: visible to the people whose belief you need, meaningful rather than cosmetic, and deliverable inside the window. For a CTO, the pattern that works: Fixing the one recurring incident class that had burned the team quarterly earns the engineering organization’s belief. The wrong early win, flashy, contested, or hollow, costs more than none.
The Onboarding Mistake That Sinks New CTOs
New CTOs are tempted to announce grand re-platforming early; rewrites declared before trust is earned unite the organization against them. Every new executive faces the standard hazards; this one is the role’s own, and knowing it in advance is most of avoiding it.
What the Organization Owes the Transition
Half of transition failures are organizational, not individual: mandates left vague, landmines undisclosed, stakeholders unintroduced, and instant performance expected. The fix costs little, a written mandate, real introductions, disclosed problems, and calendared alignment checkpoints at 30, 60, and 90 days.
From 90 Days to the Full Tenure
Ninety days is the overture; the scorecard and operating rhythm installed at its end govern the years after. The scorecard that goes live at day 90 should be the same one governing the tenure: our guide to measuring CTO performance defines those KPIs and their cadence. And if the hire is still ahead of you, our CTO interview questions guide tests for exactly the transition skills this roadmap demands.
Frequently Asked Questions
- Q: What should a new CTO accomplish in the first 90 days?
- A: Judge the quarter by its artifacts: a diagnosis the organization recognizes as true, a plan the boss has signed, one delivered win, and a live scorecard, four things, and busy-ness counts for none of them.
- Q: How long until a new CTO reaches full productivity?
- A: Expect diagnostic value immediately, decision value by the second month, and full run-rate ownership somewhere in months four through nine, faster in operational roles with short feedback loops, slower where results lag decisions by quarters.
- Q: What is the right early win for a new CTO?
- A: Fixing the one recurring incident class that had burned the team quarterly earns the engineering organization’s belief. Choose for visibility, meaning, and deliverability inside the window, and deliver it before the honeymoon’s attention fades.
- Q: How quickly should a new CTO make people changes?
- A: Fast on assessment, deliberate on process, prompt on execution: month one to see clearly, month two to decide the obvious cases, and immediate, respectful action once decided, because the team is watching whether the new leader sees what they see.
- Q: What if the job turns out different from the one described?
- A: Bring evidence to the next scheduled checkpoint and renegotiate the mandate in writing; a gap named at day 45 is a calibration, the same gap named at day 200 is a crisis with your name on it.
- Q: Who owns executive onboarding, HR or the hiring manager?
- A: The hiring manager owns it, with HR as architect and the executive as driver. Onboarding delegated entirely to HR signals the relationship’s real priority, and new executives read the signal accurately.
![](https://www.jrgpartners.com/wp-content/uploads/2025/12/tanya-gallardo.jpeg")
Tanya Gallardo
Managing Director, Executive Search & AI Talent Strategy
Tanya Gallardo is the Managing Director of Executive Search & AI Talent Strategy at JRG Partners, leading C-suite and Board engagements across key growth sectors including Technology, Financial Services, and Manufacturing.
With over 18 years of experience specializing in disruptive technology leadership, Tanya is recognized as a leading authority on talent architecture for future-focused executive roles, such as the Chief AI Officer (CAIO) and Chief Digital Officer (CDO). Her expertise lies in accurately assessing the cultural fit and technical depth required to ensure a high return on investment (ROI) for critical leadership appointments.
Prior to her role at JRG Partners, Tanya held senior roles directing global talent acquisition strategies at a major publicly-traded technology firm, advising on organizational design and succession planning for emerging executive functions. She is a recognized speaker and contributor to industry events, sharing data-driven insights on executive compensation, leadership development, and the measurable business impact of C-suite talent.
