The Full Playbook from Each Chapter Is Here

All 23 playbooks, in chapter order

Companion to The Code Takes Care of Itself · Updated 2026-09-30

Every chapter of The Code Takes Care of Itself ends on a playbook. The book prints a short version of each, enough to run the tool and read without the web. The full version is here, with every step, every example, and the “Try this with AI” prompt that goes with it.

Each page names the chapter it comes from and assumes you have read the argument there. Pick the playbook that matches the decision in front of you, and print the page if you want to write on it.

The CTO Sets the Standard the Team Works To

Write the Playbook Down and Keep It Current

Lead by Placing and Developing People Well

Earn Trust by Showing How the Work Is Going

Growth Needs Decisions Made Ahead of Demand

Build a Team That Keeps Working Without You

Tie the Playbook to What the Business Earns

In this section

  • Pick Your Top Three Coaching Priorities and Make Each Testable

    A four-step exercise: choose exactly three coaching priorities, give each a testable goal and a real event behind it, and set a dated goal from what four people say about your leadership.

  • Run the Origin Audit in Your First Sixty Days

    A five-step audit for a new seat: test the founding story against current revenue, name the game you play now, answer four questions in writing, and schedule the next audit.

  • Fill In the Three-Horizon Vision Worksheet in One Week

    A six-step worksheet, about a week of work: ground the business, inventory the advantages competitors can’t copy, then write a twelve-month, a position, and a long horizon and test the result on three audiences.

  • Define What Good Means Before You Pick Metrics

    A five-step exercise for teams called “high performing” without a checkable definition: start from each stakeholder’s scoreboard, choose a few metrics, separate coaching from scoreboard data, and review what each metric makes people do.

  • Spend One Hour on the Lineage Audit Before Writing Plays

    A one-hour diagnostic before you write plays: name an owner for your key requirements, delete what you would not create today, stop unexamined automation, test your authority, and score your cost honesty.

  • Draft One Play for One Team and Get It Right

    A six-step template for the first version of an engineering playbook: pick the play whose absence costs most, write its purpose in one sentence, trace every rule to it, co-write it, and measure it for a quarter.

  • Write Down How Your Playbook Gets Changed

    A six-step exercise that sorts plays into core and situational, names observable leading indicators, sets a review cadence and stewards, and requires a pilot before any change becomes a mandate.

  • Review the Talent Framework Every Quarter

    A four-part quarterly template: a skills-gap map, a recruiting scorecard, trajectory tracking, and a retention system, ending in a ranked hiring and development list tied to business commitments.

  • Separate What a Role Requires from What Is Merely Useful

    A five-step template that lists roles rather than titles, separates must-have from good-to-have skills, maps the roster role by role, and is reviewed every two quarters.

  • Prepare the Crisis Response Plan in Seven Steps

    A seven-step plan built before you need it: named roles, severity definitions with update cadences, one update template, a vocabulary check, a contingency inventory, a postmortem protocol, and a tabletop drill.

  • Track Each Person’s Autonomy Stage Task by Task

    A five-step tracker for every direct report, kept by task category rather than by person: a stage per category on named evidence, a review cadence, an explicit conversation, and a review after any incident.

  • Map What Each Department Needs to Hear from Engineering

    A five-step strategy built once and kept current: map each audience and its frame, build a translation table for three initiatives, set a cadence and channel, write the strategy three ways, and test it on a real stakeholder.

  • Install the Instrument Panel One Written Step at a Time

    A six-step install for your first quarter in a seat: rate the instruments you have, choose six to eight metrics, set thresholds in advance, list instrumentation debt, fit the cadence into existing meetings, and test the page on a non-engineer.

  • Keep a Living Plan for Every Relationship You Manage

    A six-step living plan: map your relationships by name, describe each honestly in one sentence, make no-ask deposits, secure informal agreement before decision meetings, give every commitment two dates, and review each quarter.

  • Check Whether You Have an Answer Before You Approve Scaling

    A six-step diagnostic to run at every growth inflection: name your threshold, score three signals, price the cost of inaction, inventory tacit judgment, decide what to protect and pause, and set the next check.

  • Revisit Architecture Bets on a Fixed Cadence

    A five-step standing exercise, quarterly for fast growth and semi-annually for stable companies: state the business trajectory, name each system’s ceiling, classify decisions by reversal cost, assign owners and triggers, and bring a business voice in.

  • Run Five Questions Before You Lock In or Defer a Decision

    Five questions to run the next time someone says “keep our options open” or “lock this down now”: dependencies, reversal cost at six and eighteen months, what you are waiting for, the owner and trigger, and execution cost.

  • Write a Tradeoff Ledger Before Any Hard-to-Reverse Decision

    A six-step ledger for any decision whose reversal would show up on a roadmap: what you gain and give up, the binding constraint, risks both ways, assumptions and a reversal trigger, who pays, and second-order effects.

  • Audit the Completion Loop When Shipping Falls Behind Generating

    A six-step audit for when shipping stops keeping pace with generating: map the loop and its owners, measure Integration Debt, find the real constraint, own Governance Latency, choose metrics, and coach a C-suite peer.

  • Build the Leadership Pipeline and Then Test It

    A five-step roadmap that builds a leadership pipeline and then tests it: name your bench, find the last real decision each person made without you, remove single points of failure, take a controlled absence, and transfer one piece of judgment.

  • Decide Now What Should Outlast Your Tenure

    A five-step blueprint that turns a long-term aspiration into actions you can take now: name a habit, find where it lives, encode it in three levers, write the customer-impact statement your successor inherits, and set a five-year trigger.

  • Turn Every Request into a Capability Ticket

    A six-step template for a request that arrives with no reasoning attached: a capability statement, an economic category, a number with a confidence level, two tests in order, and a queue sorted by category and then by the smaller value.

  • Design a Rotation Program That Fits Your Company

    A six-step design for a customer rotation program: a short exemption list, a calendared cadence, a clear completion test, one written observation each time, a route into capability economics, and leaders going first.