---
title: "The Checklist Manifesto: How to Get Things Right"
author: Atul Gawande
published: 2009
tags:
  - books
  - summary
---

# The Checklist Manifesto

## Core argument

Modern professional work has outgrown the capacity of any individual expert to do it reliably from memory. Gawande, a surgeon, argues that the humble checklist is the most underused tool for closing the gap between what we know and what we actually do.

He builds on a distinction from philosophers Samuel Gorovitz and Alasdair MacIntyre between two kinds of failure:

- **Errors of ignorance**: we fail because the knowledge does not exist yet.
- **Errors of ineptitude**: we fail because we do not correctly apply knowledge we already have.

For most of history, ignorance dominated. Today, in medicine, aviation, construction and finance, ineptitude is the bigger problem. More training and more expertise do not fix it, because the volume and complexity of what must be done exceeds what attention and memory can hold.

## Key ideas

### Why experts still fail

- Memory and attention are fallible, especially for routine steps that are easy to skip under pressure.
- People talk themselves into skipping steps that "never matter", until the one time they do.
- Checklists protect against both by making the minimum necessary steps explicit and verifiable.

### Three kinds of problems

Borrowed from Brenda Zimmerman and Sholom Glouberman:

| Type | Example | What works |
| --- | --- | --- |
| Simple | Baking a cake | A recipe |
| Complicated | Sending a rocket to the moon | Many specialists, coordination, repeatable once solved |
| Complex | Raising a child | Outcomes stay uncertain; experience helps but does not guarantee |

Checklists handle the simple parts directly. For complex work, their role shifts to making sure people **talk to each other** at the right moments.

### Two jobs a checklist does

1. **Task checks**: catch the "stupid but critical" steps (antibiotics given, right patient, right site).
2. **Communication checks**: force the team to pause, share what they know, and plan for trouble.

The construction industry is his model for the second kind. Builders manage enormous complexity with a schedule of tasks plus a separate "submittal schedule" that specifies who must talk to whom, by when, about what. Authority is pushed out to the people closest to the problem rather than concentrated in a master builder.

### What makes a good checklist

Learned from Daniel Boorman, who writes checklists at Boeing:

- **Short**: roughly five to nine items, taking about 60 to 90 seconds.
- **Only the killer items**: steps that are both dangerous to miss and actually get missed. It is not a how-to manual.
- **A clear pause point**: a defined moment when the checklist is used.
- **Choose a type**:
  - *DO-CONFIRM*: do the work from memory, then pause and confirm.
  - *READ-DO*: read each step and perform it, like a recipe.
- **Simple, exact wording** in the language of the profession.
- **Tested in the real world** and revised, repeatedly. First drafts always fail.

## Main stories and evidence

- **Boeing Model 299 (1935)**: the prototype of the B-17 crashed on a test flight because an experienced pilot forgot to release a control lock. The plane was judged "too much airplane for one man to fly". The response was not more training but the pilot's checklist, and the aircraft went on to fly safely for millions of miles.
- **Peter Pronovost's central line checklist**: five basic steps at Johns Hopkins nearly eliminated line infections. Rolled out across Michigan ICUs in the Keystone Initiative, it cut infections by about two thirds and was estimated to have saved around 1,500 lives and $175 million in 18 months.
- **Hurricane Katrina and Walmart**: when centralized command failed, Walmart did well by giving store managers authority to act and keeping them in communication. This illustrates decentralized decisions plus coordination.
- **Van Halen's brown M&Ms**: the contract clause banning brown M&Ms was a cheap test of whether the venue had read the technical rider carefully.
- **WHO Safe Surgery Checklist**: Gawande's team built a 19-item checklist with three pause points (before anesthesia, before incision, before the patient leaves the room). In a study across eight hospitals in rich and poor countries, major complications fell 36% and deaths 47%.
- **Investors**: Mohnish Pabrai, Guy Spier and others use checklists to counter "cocaine brain", the greed-driven urge to skip due diligence on an exciting deal.
- **US Airways Flight 1549**: the Hudson landing was celebrated as individual heroism, but Sullenberger and Skiles credited procedure, checklists and teamwork.
- **Gawande's own operating room**: during an adrenal tumor removal he tore the vena cava. The patient survived partly because the checklist discussion had prompted the team to have blood ready.

## Teamwork and culture

- Having team members introduce themselves by name before surgery measurably increases the chance they will speak up later. Gawande calls this an "activation phenomenon".
- Checklists redistribute power: a nurse is authorized to stop a surgeon who skips a step.
- Resistance is mostly cultural. Professionals see checklists as beneath them, an insult to expertise and a threat to autonomy. In his survey, about 20% of surgical staff disliked the checklist, yet 93% said they would want it used if they were the patient.
- He argues that professionalism should include **discipline** alongside selflessness, skill and trustworthiness. Discipline is the hardest because humans are not built for it.

## Limits and caveats

- A checklist cannot make you a skilled practitioner or think for you. It frees attention for the hard, judgment-heavy parts.
- Long, vague or impractical checklists get ignored and become box-ticking.
- A checklist imposed without buy-in or adaptation to local conditions tends to fail.

## Takeaways

- Ask of any recurring high-stakes task: which steps are both critical and easy to miss?
- Keep it short, tie it to a specific pause point, and test it in use.
- For complex work, add communication checks, not more task detail.
- Treat using a checklist as a mark of professionalism, not a lack of it.