The Checklist Manifesto
Why Checklists?
The Checklist Manifesto is a short book written by Atul Gawande detailing the uses of checklists for medical interventions. The idea behind checklists is simple: build a system to ensure that the most common errors are caught to greatly reduce overload. Like many distributions, system errors have a high density in top $n$, but also a long tail. We should build checklists to optimize against the top $n$ errors, and use domain expertise on a case-by-case basis for the long-tail. Below is the surgical safety checklist developed by Gawande for the WHO.
Like making sure everyone in the operating room knows each other by name. When introductions were made before a surgery, Gawande says, the average number of complications and deaths dipped by 35 percent.
A 35% reduction in deaths is a massive improvement, and speaks to the power of simple one-page checklists. Checklists are used by architects, construction managers, airplane pilots, militaries, and hospitals around the world. In an era with unlimited access the information there is simply too much for a single person to know everything. Checklists are not an insult to the expert, they are a tool to free up valuable mental energy to focus on the long-tail of errors. The case for checklists can be made in 3 simple points:
- Allocate Focus Efficiently - Checklists help experienced practitioners free up mental energy to focus on what’s most important
- Even the Power Dynamics - Checklists provide common authority to allow all team members to contribute regardless of experience. Gawande brought up increases in nurse communication with attending surgeons thanks to checklists. This communication increase was the change behind the massive reduction in mortality. When communication becomes a part of the process everyone communicates more.
- Simplify Complexity and Streamline Processes - Checklists make it easy to have a starting point no matter how complicated the problem.
How to Design a Checklist
Checklists run into many of the same problems as other changes in business processes. If the friction involved in implementation is too great it won’t be implemented. If a checklist is too simple or trivial, it won’t get utilized or it will fail at it’s ultimate goal. The above checklist for checklists provides the key considerations needed for proper working.