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. The transition begins well before day one
Research → commit → diagnose → change
6. 00. Before day one
Choose the transition before accepting the role
7. The market defines your choice corridor
Stage, industry, capital, and pace
8. Diagnose the transition type first
Launch, scale, realign, or recover
9. Deep research creates hypotheses
Facts → tensions → questions → tests
10. Understand where the money comes from
Customer → value → revenue → technology
11. Technology leaves outside signals
Openings, releases, outages, patents, and hiring
12. Power does not mirror the org chart
Decisions follow trust, budget, and access
13. Contradictions generate the best questions
Do not resolve tension too early
14. The interview runs both ways
They test you—you test the system
15. C. The commit point
Expectations must become a mutual contract
16. Why is this role open now?
The trigger reveals the actual assignment
17. The mandate matters more than the title
Decisions, access, and sponsorship define the job
18. Commit means a mutual contract
Outcomes · authority · resources · constraints · success
19. 30. Days 1–30
Map the real company without rewriting it
20. Open your eyes and ears first
Curiosity before certainty
21. Stabilize only a real emergency
Security, cash, people, or continuity
22. Listen to the system, not the hierarchy
Executives, engineers, sales, customers, and support
23. One question—four versions of the company
Ask about success, obstacles, decisions, and risk
24. Walk the path of money
From customer promise to recognized revenue
25. Walk the path of change
Idea → decision → code → release → effect
26. Walk the path of an incident
Signal → response → recovery → learning
27. Assess health through seven lenses
Business · culture · people · delivery · technology · morale · sustainability
28. Build the map by day 30
People · business · processes · risks · hypotheses
29. 90. Days 31–90
Validate the diagnosis and change one or two systems
30. Hypotheses must survive the data
Observation → metric → test → decision
31. Change one or two systems
Fewer bets, more completion
32. The first result should strengthen trust
Value now, capability later
33. Strategy starts with diagnosis
Diagnosis → choice → coherent action
34. Your leadership team is the lever
Clear roles, decisions, and feedback
35. A new contract exists by day 90
Diagnosis · year · changes · cadence · metrics · team
36. But red flags appear earlier
Risk runs through the entire transition
37. Before commit, flags hide in the fog
Vague role · closed access · conflicting stories
38. Promises meet reality after day one
Access · resources · behavior · cost of dissent
39. A flag needs a protocol
Notice → verify → name → agree → timebox → decide
40. 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