Reading: Atul Gawande, “The Checklist Manifesto”

In 2001, an intensive-care physician at Johns Hopkins named Peter Pronovost wrote down the five steps clinicians were already meant to follow when inserting a central-line catheter — wash hands, clean the patient’s skin with chlorhexidine, drape the patient sterilely, wear sterile gloves and gown, place a sterile dressing — and asked the nurses on his unit to stop any doctor who skipped a step. Within a year, the unit’s central-line infection rate had fallen by sixty-six per cent and the hospital had saved an estimated forty-three lives and two million dollars. Atul Gawande, the Harvard surgeon and *New Yorker* writer, opens his 2009 book *The Checklist Manifesto* with that result and proceeds to argue, across two hundred and twenty pages, that the humble written instrument the nurse used to interrupt the doctor is the most under-deployed piece of operating discipline in modern professional life.

The book is short, fast, and built around a distinction that operations practitioners will find immediately useful: the difference between simple problems (those with a single right answer), complicated problems (those that decompose into many simple sub-problems and yield to expertise), and complex problems (those whose conditions change as you act on them, so that no fixed instruction can carry the work). Gawande’s argument is that checklists are the right discipline for the first two categories — and, with care, for parts of the third — but they have to be designed for the actual work, not imposed from above as a substitute for it.

The two quotations the practice has carried out of this book and back into client conversations are these. The first: “if you’re confronted with simple and routine problems, you want the forcing function — a checklist.” The second, on what to do when the work is genuinely complex: “you push the power of decision-making out to the periphery and away from the centre. You give people room to adapt, based on their experience and expertise. All you ask is that they talk to one another and take responsibility.” The pairing matters. A checklist is not a substitute for skilled people; it is a prosthesis for skilled people working at the edge of what they can hold in their heads.

Three things in the book translate directly to the floor of a manufacturing or service operation.

A checklist is a forcing function, not a crutch. Aviation has used checklists for nearly a century — Boeing developed the modern aircraft pre-flight checklist after the 1935 crash of the prototype B-17 at Wright Field, in which the most experienced test pilot in the United States Army Air Corps killed himself by failing to release the elevator gust lock — and the discipline has not deskilled the pilot population. It has produced a workforce that knows when to follow the script and when to depart from it. The same is true on a manufacturing line.

The checklist must be made by the people who do the work. The World Health Organisation’s Safe Surgery Checklist, which Gawande’s group helped develop and which has reduced surgical deaths by forty-seven per cent in the trial sites, was iterated by surgeons, anaesthetists, and nurses from eight pilot hospitals before it earned the right to be used in any of them. Top-down checklists fail because they encode someone else’s understanding of the work; bottom-up checklists succeed because they encode the team’s own. The implication for the practice’s clients is structural: the kaizen event is the format in which a checklist of any seriousness should be authored.

The hardest checklists are the ones that pause expert work. Gawande is particularly clear-eyed about why surgeons, pilots, and other senior practitioners resist checklists: not because the checklists are wrong, but because pausing to read one is a public admission that the practitioner’s intuition is not infallible. The discipline survives only where the operating culture treats the pause as a mark of professionalism rather than a failure of it. This is a culture point, not a process point, and it is exactly the territory Lean transformations spend most of their early effort in.

The book’s clearest practical lesson — and the one most worth carrying into operations not yet ready for the larger Lean toolkit — is that a forty-five-second pause to read a five-line list, before the team begins, is one of the cheapest improvements available to almost any operation. Most operations have not adopted the discipline because they have not yet been embarrassed enough to bother. Gawande’s contribution is to record, with a surgeon’s plain prose, exactly how much embarrassment is on the table.

· · ·