Richard Rumelt

The most useful book on strategy I’ve read. Rumelt’s argument is simple and devastating: most “strategy” is actually a list of goals dressed up in strategic language. Real strategy has a diagnosis, a guiding policy, and coherent actions. Bad strategy has none of these. I apply the diagnosis-first standard to every ops problem I touch.

Richard Rumelt

The follow-up to Good Strategy / Bad Strategy. Teaches how to identify the single most important, solvable challenge and concentrate resources there. Most leaders work on the wrong problem with full conviction. This is a useful corrective.

Nick Mehta, Dan Steinman & Lincoln Murphy

The foundational text for CS practitioners building in the subscription economy. Required reading for anyone trying to understand why retention is a structural problem, not a relationship problem.

Chip Heath & Dan Heath

Six traits of ideas that survive: Simple, Unexpected, Concrete, Credible, Emotional, Stories (SUCCESS). I use this framework every time I need to get a process change adopted — adoption is a communication problem before it’s an execution problem.

Larry Bossidy & Ram Charan

Execution is the missing link between strategy and results. Bossidy identifies three processes a leader must own personally: People, Strategy, and Operations. The argument that strategic planning without operational follow-through is theater is one I’ve seen proven repeatedly.

Atul Gawande

Simple checklists prevent catastrophic failures in surgery, aviation, and construction — not because the professionals are incompetent, but because complexity creates the conditions for error. The case for building documentation and process rigor into high-stakes workflows is made well here and difficult to argue with afterward.

Jocko Willink & Leif Babin

The more useful of the two Willink books. Every leadership quality exists on a spectrum, and the discipline is knowing where you are on it. Aggressive enough but not reckless. Confident but not overconfident. Detailed but not micromanaging. The dichotomies are real and navigating them is the actual work of leadership.

Liz Wiseman

Some leaders make the people around them smarter. Others diminish them without meaning to. Wiseman’s framework is useful for self-diagnosis: most accidental diminishers think they’re helping. The “rescuer” pattern in particular is worth watching for in yourself.

Kim Scott

Challenge directly, care personally. The two-axis framework is simple enough to be usable and accurate enough to be true. Most feedback failures in organizations fall into “ruinous empathy” — caring too much about the relationship to say the thing that would actually help the person.

Erin Meyer

Eight scales for understanding how different cultures approach communication, trust, disagreement, and decision-making. Practically essential for anyone building or managing globally distributed teams. Running a ship with crew from 40+ countries made this book more useful, not less.

Molly Graham (First Round Review)

The best single piece of writing on what it actually feels like to scale as a leader. As a company grows, you have to give away the things you love most and built yourself — or you become the bottleneck. The lego metaphor is precise and the emotional honesty makes it stick.

Patrick Lencioni

Most leadership problems stem from the wrong motive. Lencioni distinguishes between reward-centered leaders — in it for the status, perks, and recognition — and responsibility-centered leaders who see the role as an obligation to serve. The test he offers is simple: do you see the difficult, unglamorous parts of leadership as a burden or as the job? Worth reading alongside the Willink books for a values anchor.

L. David Marquet

Marquet turned the USS Santa Fe — the worst-performing submarine in the US Navy — into one of the best by doing one thing: stopping giving orders. The leader-leader model he built pushed authority down to the people closest to the information. The principle applies directly to any ops function: a system only works if the people running it own it, not just execute it.

Greg McKeown

Essentialism: the disciplined pursuit of less — identify the vital few, eliminate the trivial many. Effortless is the less obvious follow-up: it’s not always about trying harder; sometimes the path is clearing the friction. Read in sequence. They build on each other.

Cal Newport

Do fewer things. Work at a natural pace. Obsess over quality. Newport’s argument against the pseudo-productivity of constant busyness is well-timed for anyone trying to do meaningful work while managing an inbox. I find the “do fewer things” principle harder to apply than it sounds and more valuable when you actually apply it.

Rory Vaden

A decision framework for tasks: eliminate, automate, delegate, or do it now. The insight I keep coming back to is the “automate” column — most people skip straight to delegation when the real answer is building a system so the decision never needs to be made again.

Paul Graham

One of the more clarifying short essays I’ve read about why meetings destroy the workday for people who build things. Makers need long uninterrupted blocks. Managers run on one-hour increments. The conflict is structural, not personal — and recognizing it changes how you schedule and what you protect.

Ajay Agrawal, Joshua Gans & Avi Goldfarb

Read this before Power and Prediction — it establishes the economic frame. AI lowers the cost of prediction; that single insight ripples through every decision a business makes about where to invest, what to automate, and which roles hold their value. Cleaner and more foundational than most AI business books.

Ajay Agrawal, Joshua Gans & Avi Goldfarb

The follow-up to Prediction Machines. Where the first book asks what AI changes economically, this one asks who wins and who loses when prediction gets cheap. The framework for thinking about “the decision” as the fundamental unit of organizational analysis is one of the more useful mental models I’ve applied to GTM systems design.

Tom Davenport & Nitin Mittal

Where Prediction Machines asks what AI changes economically, All-In on AI asks how companies actually execute the shift. Davenport profiles enterprises that integrated AI into core strategy — not as a pilot, but as the operating model. Useful for thinking through what an AI-native ops function looks like in practice rather than in theory.

Daniel Pink

Written before the current AI wave but more relevant now than when it was published. As analytical and logical tasks get automated, the abilities that hold their value are empathy, design, narrative, and synthesis. Pink named the trend early. The question is what you’re building in yourself.

Annie Duke

Decision quality and outcome quality are different things. A bad decision can produce a good outcome and vice versa. Duke’s framework for separating the two — and for getting better at assessing probabilities rather than judging by results — is directly applicable to any ops leader making calls with incomplete information.

Shane Parrish

The quality of your thinking in ordinary moments — not just high-stakes decisions — determines your outcomes over time. Parrish’s distinction between default behaviors and deliberate choices is useful for anyone who designs processes meant to produce consistent judgment at scale. The chapter on self-accountability is the one I’ve re-read most.

Daniel Kahneman, Olivier Sibony & Cass Sunstein

Bias gets most of the attention in discussions of bad judgment. Noise — the unwanted variability that makes two people evaluate the same case differently — gets less. This book makes the argument that noise does as much damage as bias and is harder to detect. Relevant for anyone designing health scoring, hiring, or evaluation systems.