Cover of The Checklist Manifesto

The Checklist Manifesto

Atul Gawande

7 ideas

  1. Failure of Ignorance vs Failure of Ineptitude

    Errors come in two kinds: those caused by not knowing enough (ignorance) and those caused by not correctly applying what we already know (ineptitude). In modern complex fields, ineptitude is now the dominant problem because knowledge has outpaced our ability to deliver it consistently.

  2. The Surgical Safety Checklist's Global Trial

    Gawande's team tested a 19-item surgical checklist across eight hospitals worldwide, including one item requiring all team members to introduce themselves by name. Major complications fell by 36% and deaths by 47%, with improvements seen even in well-resourced hospitals that assumed they were already safe.

  3. Simple, complicated, and complex problems

    Simple problems, like baking from a recipe, are solved by following steps. Complicated problems, like a moon launch, are solved by breaking them into coordinated simple problems. Complex problems, like raising a child, are unpredictable and unique. Checklists handle the routine steps, but complex problems also need structured communication so that people can adapt together to what no one could foresee.

  4. Checklists catch lapses experts inevitably make

    Human memory and attention fail most predictably on routine steps that seem too obvious to forget, especially under stress, fatigue or interruption. A checklist offloads these 'dumb' steps from memory, which frees expert judgment for the genuinely novel parts of the problem. The central line of Peter Pronovost's central-line checklist, a five-step infection protocol, cut ICU line infections dramatically by enforcing steps every clinician already knew.

  5. Designing a usable checklist

    Good checklists are short (roughly five to nine items), fit on one page, use precise simple wording, and target only the critical steps most likely to be missed. They are placed at defined pause points and are written as either DO-CONFIRM, where the team works from memory and then verifies, or READ-DO, where they perform each step as it is read. They must be field-tested and revised, because a bad checklist is vague, long and treats users as incapable.

  6. Communication checklists that push power outward

    Construction projects pair task checklists with submittal schedules that force specified experts to talk at set points, trusting the group rather than a single master builder to catch problems. In surgery, the team introduction by name and role before incision activates team members and makes nurses more likely to voice concerns. The checklist redistributes authority so that anyone who sees a problem can stop the line.

  7. Boeing Model 299 crash births pilot checklist

    In 1935 the Army's prototype B-17 crashed on takeoff because an experienced test pilot forgot to release a new gust lock, and the press called the plane 'too much airplane for one man to fly.' Rather than demanding more training, test pilots wrote a simple index-card checklist for takeoff, flight, landing and taxiing. With that checklist, crews flew 1.8 million miles without an accident, showing that complexity had outrun memory, not skill.

Save and mark ideas in the app