October 30, 2026 · Atul Gawande, The Checklist Manifesto: How to Get Things Right · Nonfiction · About 4 minutes
Before an operation, the World Health Organization's surgical safety checklist asks the team to pause. They confirm the patient's identity and procedure; they review anticipated difficulties. One item seems almost too ordinary for a medical safety document: each person should have introduced themselves by name and role.[4]
Why spend seconds on names? The person who notices missing equipment may not lead the operation. The WHO says introductions establish who is in the room; speaking once may make a junior member more likely to voice a later concern.[4][2] The checklist creates a moment in which separate expertise can meet.
In an earlier essay that develops the problem behind The Checklist Manifesto, Gawande tells an altogether different medical story: a three-year-old girl pulled from an icy pond after a long time underwater. Her survival required rescue, transport, surgery, intensive care, and many things going right in sequence. That is an example of extreme complexity, not a case in which a checklist rescued her. Gawande uses it to show how difficult it is to deliver everything modern medicine can do for a single person.[6]
My reading of the book is that competence is not only what each expert knows. It also depends on the bridges between them. Gawande's account extends beyond surgery to other complex work; he argues that experts need help making reliable use of what they already know.[9] A brilliant surgeon cannot act on a concern that nobody feels permitted to say aloud; an excellent nurse cannot fix equipment that the institution has not supplied. In an earlier essay on intensive-care checklists, Gawande describes Peter Pronovost's central-line project: nurses were authorized to stop doctors who skipped infection-prevention steps. When hospitals tried to spread the practice, leaders also had to make the needed antiseptic and full-size sterile drapes available.[6]
That last detail matters. A checklist can record what ought to happen while the system makes it impossible. The paper alone was not the intervention; permission to speak, reliable supplies, and institutional support were part of the work. It asks whether the person closest to a problem can both notice it and do something about it.[6]
Nor should every activity be reduced to boxes. A checklist cannot contain every possible complication or substitute for judgment when something unexpected happens. The WHO's own surgical checklist says it is not comprehensive and encourages local adaptation.[8] Its strength is narrower: put a few essential checks and conversations in the path of a recurring, consequential task. If a list grows so long that nobody can use it, or becomes a way to punish the person who raises a concern, its purpose has been lost.
Consider a small team about to release a change to a payment flow. Everyone has reviewed their own portion: engineering tested the code; design checked the screens; support prepared a response. But a customer might see the new price without understanding when a charge begins. This is my example, not one from Gawande. A short pre-release pause could ask: What exactly will change for the customer? What could fail? Who can stop the launch, and where will that concern be heard? The point is not to create an elaborate sign-off ritual. It is to bring the unspoken assumption into the room while there is still time to change it.
A pause can also reveal a resource problem. If support cannot see the rollout timing, the right action is not to add “inform support” to a list and blame them later. Give them access to the schedule and a real channel to flag confusing cases. If the team repeatedly ignores a check, ask whether it is poorly designed or whether the underlying conditions prevent people from doing it.
A two-minute exercise: Pick one recurring handoff this week. Write three questions: “What must be true before we proceed?” “Who might see a problem I cannot?” “Can that person actually stop or change anything?” Ask the last question especially if the handoff already has a checklist.
The most valuable line may invite someone to speak. A good pause makes room for skill that would otherwise remain silent.
[2] https://www.who.int/news-room/questions-and-answers/item/safe-surgery-saves-lives-frequently-asked-questions — WHO Safe Surgery Saves Lives FAQ
[4] https://www.who.int/docs/default-source/patient-safety/9789241598590-eng.pdf — WHO Surgical Safety Checklist implementation manual
[6] https://www.newyorker.com/magazine/2007/12/10/the-checklist — Atul Gawande, A Life-Saving Checklist
[8] https://www.who.int/docs/default-source/patient-safety/9789241598590-eng-checklist.pdf — WHO Surgical Safety Checklist (2009)
[9] https://atulgawande.com/book/the-checklist-manifesto — Atul Gawande — The Checklist Manifesto