Training

The Checklist

A brand-new bomber crashed because one expert pilot forgot a single step. The fix was not a better pilot. There was no better pilot. The fix was a piece of paper.

Tim Kinzie@Timatsu · Training · 11 min

In 1935 the Army Air Corps put its newest bomber in the air, a machine so advanced it was supposed to win the next war almost by itself. It crashed on takeoff and killed the crew. The pilot was not a rookie. He was one of the most experienced test pilots alive. The cause, when they found it, was almost insulting in how small it was. He had forgotten to release a single lock before takeoff. The plane was simply too complex to fly on memory alone, even for an expert, and in a way especially for an expert. There was no better pilot to reach for. So they reached for a piece of paper instead, a pilot's checklist a few items long, and that same aircraft went on to fly millions of miles without a serious accident.

The plane in that story has a name. It was Boeing's Model 299, and after the crash one newspaper wrote it off as too much airplane for one man to fly. With a short checklist it became the B-17 Flying Fortress. Nearly thirteen thousand were built, and they flew the war they were designed for.

That is the whole lesson in one story. Skilled people rarely fail because they lack knowledge. They fail because knowing what to do and reliably doing it, under pressure, on a loud day, for the thousandth time, are not the same skill. A checklist does not make you smarter or more talented. It catches the small, stupid, deadly lapses that have nothing to do with how good you are, and it hands your actual skill back to you for the part no list can ever do.

Two Kinds of Errors

Start with a distinction that quietly reorganizes how you think about failure. There are two ways to get something wrong. The first is ignorance: you do not know enough yet, so you make the wrong call. The second is ineptitude, a harsher word than it deserves: you know exactly what to do, and you do not do it, or you do it out of order, or you drop a piece. In any field you have actually put in the years on, ignorance is rare. Ineptitude, the avoidable miss, is where nearly all the real damage lives.

Failure One Errors of Ignorance You do not have the knowledge yet. The fix is to learn, study, train, get more reps.

Failure Two Errors of Ineptitude You have the knowledge and fail to apply it. The fix is a checklist.

A checklist does nothing for ignorance. You cannot check your way to knowledge you do not have. It is built entirely for the second failure, the one that actually gets us, and the cruel twist is that this one gets more dangerous as you improve, because experience is exactly what convinces you that you no longer need the list.

Why Memory Fails Under Load

You do not forget steps because you are careless. You forget them because attention is finite and the day is loud. The steps that get dropped are almost never the hard ones. They are the obvious ones, so obvious that skipping one feels impossible, right up until it happens. Here is what quietly eats your recall.

Routine breeds blindness: The step you have done a thousand times is the one your mind quietly stops seeing.
Interruptions drop stitches: A phone call mid-task, and a step vanishes from the sequence without a sound.
Pressure narrows focus: Under stress you lock onto the hard part and lose the simple ones entirely.
Confidence skips checks: The better you get, the more you trust a memory you probably should not.

But the deeper power of a good checklist is not the memory net. It is that it forces the team to talk. It makes people stop, say the plan out loud, name the risks, and confirm who is doing what before the work starts. Most disasters are not caught by one hero noticing at the last second. They are caught in that conversation, by the quietest person on the job finally being handed a structure that gives them permission to say the one thing that saves it.

Where It Was Proven

This is not a productivity theory I am hoping works for you. The most demanding fields on earth run on checklists precisely because the stakes were too high to keep trusting memory.

The lesson itself has a source worth naming. Atul Gawande, a surgeon, spent years studying why experts fail and put the answer in a 2009 book called The Checklist Manifesto. He did more than write about it. He led the study behind the surgery numbers below, one short checklist run in eight hospitals around the world, from London to rural Tanzania, with the results published in the New England Journal of Medicine. I did not invent this idea. I am reporting it, from the man who proved it where a skipped step kills.

Aviation: The discipline that started with that bomber now lives in every cockpit. No professional pilot takes off without running the list, however many thousand hours they have.
Surgery: A short safe-surgery checklist, tested across hospitals worldwide, cut major complications by about a third and deaths by nearly half. Same surgeons, same rooms, one list.
Construction: Buildings stand because schedule and submittal checklists force hundreds of trades to confirm their work in sequence. The list is the build’s nervous system.
High finance: Disciplined investors run every deal through the same fixed checklist, so excitement and ego never quietly skip the step that would have mattered.

What Makes a Good Checklist

Most checklists fail, and they fail the same way. Someone sits at a desk, tries to capture every possible step, and produces a long, exhaustive document that no one will ever actually run. A good checklist is almost aggressively short, and ruthless about what earns a line. First, know which of the two kinds you are building.

Type One Do-Confirm Do the work from memory and experience, then pause and confirm the critical items got done.

Type Two Read-Do Read each step and do it as you go, like a recipe. For tasks where the order is the whole risk.

Then hold it to a few hard rules. Most of the discipline is in what you leave out.

Short: Five to nine items per pause point. The moment it turns into a manual, no one reads it, and an unread checklist protects nothing.
Killer items only: The steps that actually get skipped and cause real damage. Leave the obvious-and-harmless off entirely.
Clear pause points: A defined moment to stop and run it. "Before I hit send," not a vague "sometime later."
Tested and revised: Bad checklists are written at a desk and never touched again. Good ones are sharpened on the job, one caught mistake at a time.

The Template

Here is the part most versions of this lesson leave out: the actual template. This is the blank I use, stripped to the parts that carry weight. Copy it, fill it in for one task, and start running it.

The Checklist Template

Taskthe exact repeatable moment

TypeDo-ConfirmRead-Do

Run it whena defined pause point

The Items 5 to 9 killer items

Last updatedrevise it on the job

Why each part earns its place.

Task: Name the specific repeatable moment ("send a client proposal"), not a broad area ("sales"). A checklist protects one recurring point, not a topic.
Type: Do-Confirm for work you know cold and cannot afford to slip on. Read-Do for rare tasks, or ones where the order itself is the whole risk.
Run it when: Pick the exact pause point you cannot miss. A concrete trigger beats good intentions every time.
The items: Only killer items, the ones skipped often that hurt badly. Five to nine. If you need more, you probably need two checklists.
Last updated: The list is alive. Every near-miss it catches becomes a new line. A checklist that never changes is already rotting.

And here it is filled in for a task most of us do all the time, so you can see the shape of a real one.

Worked Example Sending a Client Proposal

TypeDo-Confirm

Run it whenbefore I hit send

Scope matches exactly what we agreed on the call
Price and payment terms are correct and current
Their name, company, and dates are right (no leftover text from the last one)
Every link opens and every attachment is attached
One specific, personal line that proves I listened
The next step is stated plainly (what happens after they say yes)
Read it out loud once, for tone and typos

Download the Template Plain text. Copy it into your notes, your docs, or wherever the work already lives.

Field Work

The Objections, Because I Have Heard Them All

Every time I teach this, the same three objections stand up, so let me answer them here and save us the meeting. The first is "I am too experienced for this." Read the bomber story again. The pilot who died was the most experienced man available, and his experience was not incidental to the crash, it was load-bearing. Expertise is what earns you the confidence to skip the check, which is exactly why the error rate of experts is not zero and why every airline captain alive still runs the list. The checklist is not for the version of you having an ordinary day. It is for the version having the worst one, and you do not get to pick which version shows up.

The second is "it will kill my flow." It does the opposite, and the mechanism is worth understanding. Flow dies when part of your attention stays behind to babysit the details, the little background process asking whether you remembered the attachment. Hand the babysitting to the list and the whole mind is free for the judgment work, which is the only place flow ever lived. Pilots are not less focused for running a checklist. They are focused on flying, because the list is holding everything else.

The third is "my work is creative, it cannot be reduced to a list." Correct, and nobody asked it to be. You do not checklist the creativity. You checklist the perimeter around it, the setup, the handoff, the send, the fifty mechanical steps that bracket the creative one, so that a dropped detail never gets to undo the work the talent did. The surgeon's checklist does not perform the surgery. It makes sure the surgery the surgeon performed is the one the patient gets credit for. Same deal, lower stakes, and the same quiet dividend: once your own list is running, hand it to the next person who does the task, and it stops being your habit and becomes the standard. That is the moment a private discipline turns into an operating asset, which is what Artifacts are for.

Build Your First One

Do not try to checklist your whole life. That is how you end up with a binder nobody opens. Pick one task you do every single week, the one where a slip actually costs you something, and build a single short checklist for it with the template. That is the entire assignment.

Then run it five times before you allow yourself to judge it. The first run will feel slow and faintly embarrassing, like reading instructions for something you obviously know how to do. Run it anyway. By the fifth time it will have already caught something, quietly, that would have cost you a client, an hour, or a night of sleep, and you will finally understand why the best people in the highest-stakes work on earth would not dream of going without one.

One last thing, because it is the idea underneath this whole lesson. I call objects like this Artifacts: external, durable things that carry the weight of a decision so the mind no longer has to. A checklist is the smallest Artifact there is, and it behaves the way every good one does. Once it exists, it does not negotiate. It executes.