The Playbook

First-Time CTO?
Start here.

The first 12 months in the CTO seat are where most leaders either find their footing or drift. This is the playbook — assembled from the readiness framework and the patterns we see across new CTOs.

24
Guides curated
5
Leadership dimensions
12 mo
Coverage window
Free
Always

What this playbook addresses

The first 90 days

Listening tour, quick wins, team assessment, and the relationships you build (or don't) in the opening window.

Building the readiness

The five-dimension framework — technical, people, business, communication, self-management — and how to grow each.

Leading the AI shift

Strategy, build vs buy, team structure, and the new skills the role demands as engineering changes.

The role itself

What a CTO actually does, how it differs from VP Engineering, and what the day-to-day looks like.

What the playbook covers

First-Time CTO Playbook
  • The first 90 days

  • Building the readiness

    • Technical
    • People
    • Business
    • Communication
    • Self-management
  • Leading the AI shift

  • The role itself

The playbook, by topic

Every guide below is written for someone who is in the seat right now — not aspirational, not generic. Read in order, or jump to what you're working on this week.

Guides in each topic

Count of published guides, by topic

  1. Career3 guides
  2. Assessment1 guide
  3. AI & Strategy4 guides
  4. Leadership8 guides
  5. Comparison1 guide
  6. Education3 guides
  7. Research3 guides
  8. Skills1 guide

AI & Strategy

Leadership

Know where you stand before you pick what to work on.

The free CTO Readiness Assessment scores you across 5 leadership dimensions in 10 minutes. Use the result to decide which guide above is worth reading first.

Take the Assessment
What your result looks like

Example result: an illustration, not real data. Yours is drawn from your own answers.

Question 5 of 21Technical Leadership

A critical technical decision: rebuild vs. incrementally refactor. Your team is split 50/50. What do you do?

  • AJust rebuild it — we need a fresh start
  • BKeep patching — a rebuild is too risky
  • CCreate a decision framework weighing risk, cost, and business impact, then present options to stakeholders
  • DAsk the team what they think and go with the majority
  • EDefer to what worked at my previous company