September 3, 2026 · Stratoplan
The CTO’s First 90 Days
Choose the role, negotiate the mandate, and pass probation
/ The CTO’s First 90 Days · Stratoplan 2026
Slide contents
1. The CTO’s First 90 Days
Choose the role, negotiate the mandate, and pass probation
2. They start before day one
Your first working day is already mid-transition
3. CTO is not one job
The same title hides different assignments
4. Choose the assignment, not the title
Evaluate the transition, mandate, and price of success
5. −30. Before day one
Choose the transition before accepting the role
6. The market defines your choice corridor
Stage, industry, capital, and pace
7. Diagnose the transition type first
Build, scale, restore, or integrate
8. Deep research creates hypotheses
Facts → tensions → questions → tests
9. Understand where the money comes from
Customer → value → revenue → technology
10. Technology leaves outside signals
Openings, status page, releases, talks, and the product itself
11. Power does not mirror the org chart
Decisions follow trust, budget, and access
12. Contradictions generate the best questions
Do not resolve tension too early
13. The interview runs both ways
They test you—you test the system
14. 00. The commit point
Expectations must become a mutual contract
15. Why is this role open now?
The trigger reveals the actual assignment
16. The mandate matters more than the title
Decisions, access, and sponsorship define the job
17. Commit means a mutual contract
Outcomes · authority · resources · constraints · success
18. 30. Days 1–30
Map the real company without rewriting it
19. Open your eyes and ears first
Executives, engineers, sales, customers, and support
20. Stabilize only a real emergency
Security, cash, people, or continuity
21. One question—four versions of the company
Ask about success, obstacles, decisions, and risk
22. Walk the path of money
From customer promise to recognized revenue
23. Walk the path of change
Idea → decision → code → release → effect
24. Walk the path of an incident
Signal → response → recovery → learning
25. Assess health through seven lenses
Business · stakeholders · delivery · quality · reliability and security · people · sustainability
26. Build the map by day 30
People · money · flow · risks · hypotheses · open questions
27. 90. Days 31–90
Validate the diagnosis and change one or two systems
28. Hypotheses must survive the data
Observation → metric → test → decision
29. Change one or two systems
Fewer bets, more completion
30. The first result should strengthen trust
Value now, capability later
31. Strategy starts with diagnosis
Diagnosis → choice → coherent action
32. Your leadership team is the lever
Clear roles, decisions, and feedback
33. A new contract exists by day 90
Diagnosis · year · changes · cadence · metrics · team
34. But red flags appear earlier
Risk runs through the entire transition
35. Before commit, flags hide in the fog
Vague role · closed access · conflicting stories
36. Promises meet reality after day one
Access · resources · behavior · cost of dissent
37. A flag needs a protocol
Notice → verify → name → agree → timebox → decide
38. Start before day one
Research · contract · listen · validate · choose
The CTO’s First 90 Days
Continue with the full longread and the Book Cube channel for annotated source notes
Alexander Polomodov, Technical Director & Fellow, T-Technologies
@Book_Cube