Halt and Catch Fire

2x Activation Energy for Change

A new bet must grow at a multiple of your baseline to matter—don't dribble it in.

Autonomy at the VP Level

Place decision autonomy at the VP layer — not the leaves, not the top — to maximize thinking without producing chaos.

Build Infrastructure, Not Features

Ask 'what has to be true so anyone could build this in an hour?' and build that instead.

Peak Performance3 steps

Calories Per Hour: Intensity Over Hours

Get more done per minute instead of working more minutes, then go home.

Centralized vs. Decentralized Org Choice

Pick your org model from your product strategy: speed (Amazon) or unified experience (Apple), and accept its cost.

Mindset3 steps

Choose the Hard Path

When choosing between options, pick the harder one because it wins whether or not it works out.

Do the Opposite

Study what everyone's doing not to copy it, but to find the 180 that stands out.

Communication4 steps

Explain-It-to-Prove-You-Understand-It

Force yourself and others to explain decisions; if you can't articulate it, you probably don't understand it.

Innovation4 steps

Fault-Tolerant User Interfaces

Design your UI to match the real hit-rate of your machine learning, not a fantasy of 100% accuracy.

Self-Mastery3 steps

Find Sparring Partners, Not Mentors or Coaches

Seek peers in the ring with you who'll throw real punches—not advice from the sidelines.

Marketing3 steps

Growth Is a System (Acquisition–Retention–Monetization)

Change one part of the growth system and you change them all—so fix the true source.

Inspect the Work, Not the Person

Judge people by their actual output, not by how they talk in a conversation.

Job Trials Over Interviews

Interviews don't predict performance; make the interview as close to the real job as possible.

Productivity4 steps

Meeting Armageddon

Once a year, delete every recurring meeting and forbid new ones for two weeks.

Self-Mastery4 steps

Merge With the Unreasonable

Don't try to become a visionary; find one and connect your APIs to theirs.

Pair Programming as a Management Tool

Two people on one computer isn't half the code, it's the fastest path to the right code.

Players, Coaches, Captains

Split leadership into on-field captains and sideline coaches so top ICs never leave the game.

Mindset4 steps

Problems Never End (Be a Problem-Solving Machine)

Stop hoping the next fix makes it easier; reframe success as earning harder problems.

Marketing4 steps

Recall vs. Discovery Interface Split

Match interface density to user intent: dense grids for recall, low-density sound-rich feeds for discovery.

Innovation4 steps

Separating Change-Aversion from Real Problems in a Redesign

After a redesign, split 'upset because it changed' from 'upset because it's worse' before you react.

Solving for Everyone Is Solving for No One

Get specific about who you're NOT for—that guardrail is stronger than defining who you are.

Tell Me What It Takes to Win, Then Tell Me the Costs

Ask for the un-watered-down plan to win first; negotiate the costs down second.

Self-Mastery3 steps

The Personal Values Framework for Career Decisions

Write down what you actually care about, then reject anything that violates it, no matter how shiny.

The Six-Week Review Operating Cadence

Short, frequent check-ins where leaders pair on problems, not catch you slacking, create velocity.

Strategy5 steps

The Use Case Map (Use Cases, Not Personas)

Define what to build and how to grow from the use case, not the persona.

Strategy3 steps

The Year Is Made in the First Six Months

Because buying cycles lag, your annual number is set by what you ship in H1, not H2.

Productivity4 steps

Think It, Build It, Ship It, Tweak It

Four product phases where spend rises stage by stage — so you must retire risk before the money starts.

Mindset3 steps

Three-Model Triangulation

Apply three different mental models to a problem; agreement across them sharply raises your odds of being right.