The Checklist Manifesto: How To Get Things Right

I realized the handbook was comprised not of one checklist but of scores of them. Each one was remarkably brief, usually just a few lines on a page in big, easy-to-read type. And each applied to a different situation. Taken together, they covered a vast range of flight scenarios.

The fear people have about the idea of adherence to protocol

is rigidity. They imagine mindless automatons, heads down in a checklist, incapable of looking out their windshield and coping with the real world in front of them. But what you find, when a checklist is well made, is exactly the opposite. The checklist gets the dumb stuff out of the way,

When you’re making a checklist, Boorman explained, you have a number of key decisions. You must define a clear pause point at which the checklist is supposed to be used (unless the moment is obvious, like when a warning light goes on or an engine fails). You must decide whether you want a DO-CONFIRM checklist or a READ-DO checklist.

Much of our work today has entered its own B-17 phase. Substantial parts of what software designers, financial managers, firefighters, police officers, lawyers, and most certainly clinicians do are now too complex for them to carry out reliably from memory alone. Multiple fields, in other words, have become too much airplane for one person to fly.