Forkable CTO
← Back to Frameworks
FRAMEWORK / cto-foundation

The CTO Foundation

What to do in your first 30 days to establish authority.

Framework: The 30-60-90 Day CTO Onboarding

  • Description: This is your roadmap for a smooth transition into the role. It ensures you build a deep understanding of the business and the tech stack before you start making major changes, helping you earn the team's respect from the start.
  • Origin & Attribution: Michael Watkins established this approach in his seminal book The First 90 Days.
  • Context & Heritage: This evolved from sales ramp-up plans where new starters had to show they understood the product before hitting targets. It also draws on FDR’s 100-Day Plan, which remains the global benchmark for measuring the early impact of a new leader.

The Framework

  • Days 1–30 (The Discovery Phase): This is your immersion month. You are auditing the tech stack, reviewing technical debt, and meeting the team. Your goal is to find the hidden risks—like security gaps or fragile infrastructure—that could impact stability early on.
  • Days 31–60 (The Diagnosis Phase): Start connecting the dots. Deliver a few small, meaningful improvements to show you are there to support the team. This is when you draft your technical vision and assess whether the current team structure aligns with future goals.
  • Days 61–90 (The Execution Phase): Now you take full ownership. Finalise the roadmap, secure the budget, and set clear KPIs. You move from asking questions to setting the technical direction for the company.

Metrics & Success Indicators

  • Quantitative Metrics:
    • Onboarding Speed: Time taken to gain full administrative access to repos, cloud infrastructure, and financial reporting.
    • Initial Impact: Successful delivery of the 2-3 quick wins identified in your second month.
  • Qualitative Success Indicators:
    • Stakeholder Buy-in: The CEO and Product leads are fully aligned with your 90-day findings and future plan.
    • Team Trust: Engineers feel you have a solid grasp of their challenges and are actively working to resolve bottlenecks.

Prerequisites & Dependencies

  • Full Visibility: You need read-only access to the entire ecosystem—code, logs, and cloud expenditure—from day one.
  • Strategic Buffer: Agreement from leadership that your first few weeks are for assessment rather than immediate feature delivery or bug fixing.

Customisation (How to Fork)

  • For Startups: Move faster. Aim for a 15-30-45 day cycle if the runway is short and the team is small.
  • For Large Organisations: Extend the discovery phase. Navigating established politics and complex legacy systems usually takes the full 30 days.

The Translation Layer (Communication)

  • To the Board: I am ensuring our technology investments are directly enabling our commercial objectives.
  • To the Engineers: I am here to remove the friction and technical debt that gets in the way of your best work.

Similar Frameworks & Tools

  • Other Options: The 5 Cs of Onboarding (Compliance, Clarification, Culture, Connection, Confidence).
  • Good Tools: Use a SWOT analysis for the initial audit and a RACI matrix to clarify roles and responsibilities.

Recommended Reading

  • The First 90 Days (Watkins): The core logic for any executive transition.
  • The Phoenix Project (Kim): Excellent for identifying operational bottlenecks and understanding team flow.

Summary (TL;DR)

Don’t rush to change everything in the first week. Spend the first month learning the context, the second month identifying improvements, and the third month executing your long-term strategy.

Action Plan

  1. Immediate Step: Schedule 1:1 sessions with your direct reports and key peers. Focus on listening to their pain points.
  2. Information Gathering: Request access to recent incident reports and the last six months of cloud infrastructure billing.
  3. Core Focus: Resist the urge to dive into the code yourself. Your role is to optimise the system and the team, not just the individual tasks.