Most people assume checklists are training wheels — something beginners lean on until they know better. But when Chesley Sullenberger lost both engines over the Hudson River in 2009, his first officer worked through a restart checklist mid-crisis, and after the plane hit the water, the co-pilot ran an evacuation checklist to get 155 people out alive. When Apollo 13’s oxygen tank exploded, flight director Gene Kranz didn’t improvise from memory — he split his team in three, one group writing procedures, another turning them into step-by-step checklists for the crew, another making sure the sequence wouldn’t overload what little power the crippled spacecraft had left. Structural engineer Joe Salvia runs skyscraper construction the same way, coordinating dozens of specialized teams through a checklist-style schedule rather than trusting any one expert to hold the whole building in their head.
None of these people needed a checklist because they didn’t know what they were doing. They needed one because they knew, better than most, how easily even the right knowledge slips through the cracks under pressure.
That’s the real paradox. Not why novices use checklists, but why the most capable people — pilots with decades in the cockpit, engineers who’ve built dozens of towers, flight directors who’ve run entire missions — never stop relying on them.
Surgeon and writer Atul Gawande, who spent years studying exactly this question before building a surgical safety checklist now used in operating rooms worldwide, argues in his book The Checklist Manifesto, that expertise doesn’t eliminate human limitations. It just means you’ve learned to respect them. A checklist isn’t a sign that you don’t know what you’re doing. It’s a sign that you know how memory, attention, and willpower actually behave under pressure — and you’re planning around it instead of hoping for the best.
Here’s what checklists really do for your brain:
1. They reduce mental effort
Psychologist George Miller’s classic finding was that working memory can only hold a handful of items at once. When you’re carrying ten tasks in your head, you’re not just remembering them — you’re spending energy holding onto them, which leaves less for the task in front of you.
A checklist offloads that job. The page holds the information so your brain doesn’t have to. Instead of alternating between planning and doing, you just do. This is also why checklists cut decision fatigue: rather than repeatedly asking “what should I do next?”, you simply look at the list and act. As Roy Baumeister’s research on willpower suggests, every one of those small decisions quietly drains a limited resource — a checklist saves that resource for the work itself.
2. They reduce uncertainty
A lot of anxiety isn’t really about the work. It’s about the nagging feeling that you’ve forgotten something. Our minds don’t sit comfortably with unresolved, open-ended situations — and an unwritten to-do list is exactly that: a pile of unresolved commitments.
Writing everything down doesn’t make the work smaller; it makes the uncertainty smaller. You know where everything stands. That, on its own, creates a sense of control — even when the rest of the day is chaotic.
3. They create visible progress
Much of real work is invisible while it’s happening. Writing, studying, cleaning, coding — you can labor for hours without anything to show for it. A checklist manufactures visible proof that something moved forward.
This matters more than it sounds like it should. Bluma Zeigarnik’s research showed that unfinished tasks stay mentally “active” — nagging at you — until they’re resolved, which is part of why crossing something off provides such a distinct sense of closure. And Teresa Amabile’s research on workplace motivation found that small, visible wins are one of the most reliable drivers of continued motivation. Each checked box isn’t just record-keeping; it’s a tiny hit of momentum that makes the next box easier to start.
4. They simplify complexity
“Write a book” is not a task — it’s a category. “Clean the house” is vague. But “outline,” “draft chapter one,” “vacuum,” “laundry” — those are actions you can actually start.
Checklists force vague intentions into concrete steps. In doing so, they often reveal what doesn’t need to happen at all — sometimes the most useful part of making the list is discovering what falls off it. It’s the same principle Kranz’s team relied on when they broke “bring the crew home safely” into a precise, tested sequence of power-up steps, and the same one Salvia relies on to turn “build the tower” into a coordinated schedule dozens of teams can actually follow. Complex, high-stakes work becomes manageable not by making people smarter, but by breaking it into steps small enough that nothing critical slips through.
5. They change behavior
Writing something down increases the odds you’ll actually do it — a simple form of commitment. Repeated daily or weekly, checklists turn deliberate effort into routine; a morning checklist done enough times stops requiring willpower at all.
They also make interruptions cheap. If someone pulls you away mid-task, you don’t have to reconstruct where you were — the list tells you. And your checklist for today is really a set of instructions written for tomorrow’s tired, distracted self, who will be grateful someone thought ahead.
3 Tips on Making a Checklist
#1. Keep it lean. Include only the steps people actually forget, not every step
A checklist isn’t a full instruction manual — it’s a memory aid for the specific points where skilled people make mistakes under pressure or distraction. Gawande calls these “killer items.” If a step is obvious or automatic for anyone doing the task, leave it off; padding the list with obvious steps trains people to skim past all of it, including the parts that matter.
#2. Choose the right type: DO-CONFIRM vs. READ-DO
For tasks you don’t do often:
READ-DO: read each step, then perform it, one at a time. Best for tasks you don’t do often like assembling furniture or trying a new recipe.
For tasks you do often:
DO-CONFIRM: do the work from memory/experience, then pause and run the checklist to confirm nothing was missed — best for tasks you already know well (a pilot’s pre-flight check, your revision pass on a draft).
#3. Use precise, binary language. Think of a it as an instruction step.
“Make sure the code works” gives you a box to check, but no instructions for how to verify that — you could tick it off after running a cursory test that doesn’t cover different scenarios. “Run the test suite and confirm all tests pass,” with subtasks underneath covering a good range of scenarios, tells you exactly what actions to take and gives you an unambiguous finish line: either they passed or they didn’t.
Same gap between “review the sources” and “confirm every claim has at least one citation” — the first is a goal, the second is an instruction you can actually execute and verify.
Where This Leaves Us:
Checklists don’t compensate for a lack of ability. They compensate for being human — for the fact that memory is limited, attention wanders, and willpower runs out over the course of a day. Novices need checklists because they don’t yet know what to do. Sullenberger, Kranz, Salvia, and Gawande needed them because they knew, better than anyone, how easily even the right knowledge can slip through the cracks under pressure.
That’s not a limitation to outgrow. It’s a permanent feature of how minds work — the smartest people are the ones who stopped fighting it and plan for it instead.
Leave a Reply