startup-cto-handbook

The Startup CTO's Handbook — Skill Guide

Source: "The Startup CTO's Handbook: Essential Skills and Best Practices for High Performing Engineering Teams" by Zach Goldberg (2023) Reference: ctohb.com | startupctohandbook.com

Overview

This skill encapsulates the core principles and actionable frameworks from the book. It's organized into three domains matching the book's structure. Read the relevant reference file for the domain the user is asking about.

Quick Navigation

User is asking about...	Read this reference
Management, coaching, 1:1s, delegation, communication, hiring, interviewing, onboarding, performance reviews, team structure, remote work, CTO types, working with CEO/CFO	references/people-and-culture.md
Tech culture pillars, tech debt, roadmaps, sprint processes, workflow, estimates, RFCs, developer experience	references/tech-team-management.md
Architecture (monolith vs microservices), API design, coding patterns, DevOps, CI/CD, containers, testing, security, source control, production incidents	references/tech-architecture.md

Core Philosophy

The golden rule of management: do what it takes to get the best out of your team. Your performance as a manager is measured by the performance of your team. This requires humility — consistently putting the needs of direct reports above your own.

The Skill Tree Mental Model

Think of your career as an RPG skill tree. Moving from IC to management means starting at Level 1 in an entirely new branch. Technical skills are necessary but insufficient — you need people leadership, architecture thinking, and general decision-making skills.

Key Frameworks

Three Stages of Problem-Solving:

1. Ingest — Collect data via docs, 1:1s, active listening. Stop when patterns repeat.
2. Synthesize — Step back for a few days. Form hypotheses from different angles.
3. Act — Execute a plan, validate results, restart the loop if needed.

Two Types of Decisions (Bezos framework):

• Type 1: Irreversible — decide methodically, carefully, slowly. Example: choice of programming language.
• Type 2: Reversible — decide quickly with high-judgment individuals. Example: button color.
• Most day-to-day technical decisions are Type 2. Using Type 1 process for Type 2 decisions leads to slowness.

Team Decisioning Models:

• Independent: Manager decides alone → fastest, least buy-in.
• Straw Man: Manager drafts, team iterates → medium time, good buy-in.
• Codevelopment: Build from scratch together → slow, maximum buy-in.
• Optimize for buy-in: missionaries, not mercenaries.

Breaking Ties: Three narratives:

1. "Your way — you made a convincing argument."
2. "My way — I have broader context, here's why."
3. "My way — it's a tie, and I'm accountable for the outcome."

Servant Leadership

Adopt servant leadership: focus on empowering others, building transparency, communication, collaboration, and growth. Ask: "Which option enables the team to do their best work?"

The Three Types of Startup CTO

1. Tech-Focused (Chief Architect): Forward-thinking strategy, architecture, POCs, fewer direct reports.
2. People-Focused (VP of Engineering): Hiring, culture, managing ICs and managers, internal processes.
3. Externally-Focused (Head of Technical Sales): Blog posts, conferences, sales support, developer evangelism.

Most founder CTOs start tech-focused. If the company needs a focus that isn't your superpower, delegate it — hire a VPE or developer evangelist accordingly.

Recommended Reading (from the book)

• Managing Humans — Michael Lopp (management fundamentals)
• Radical Candor — Kim Scott (communication)
• The 7 Habits of Highly Effective People — Stephen Covey (time management)
• Getting Things Done — David Allen (productivity)
• Extreme Ownership — Jocko Willink (ownership and accountability)
• High Output Management — Andy Grove (management systems)
• Immunity to Change — Robert Kegan (delegation)
• Thinking Fast and Slow — Daniel Kahneman (avoiding bias)
• Escaping the Build Trap — Melissa Perri (product management)
• Team of Teams — Stanley McChrystal (culture)
• Good Strategy/Bad Strategy — Richard Rumelt (strategy vs goals)
• Scrum — Jeff Sutherland (agile processes)
• The Phoenix Project — Gene Kim (DevOps culture)
• Domain-Driven Design — Eric Evans (architecture)
• Scaling Up — Verne Harnish (hiring/topgrading)

How to Use This Skill

When the user asks a question:

1. Identify which domain(s) the question falls into using the Quick Navigation table above.
2. Read the relevant reference file(s) to find specific guidance, frameworks, and actionable advice.
3. Provide a concrete, actionable answer grounded in the book's principles. Include relevant frameworks, checklists, or best practices.
4. Where appropriate, mention the recommended reading for deeper dives.
5. Adapt advice to the user's context — team size, company stage, and specific challenges matter.