The Checklist Manifesto: Why High Performers Use Checklists — Doctors, Pilots, and Engineers

July 2026

There’s a quiet assumption a lot of people carry into their careers: checklists are for beginners. Once you’re actually good at something, the thinking goes, you shouldn’t need one — real expertise means holding it all in your head. It’s a natural assumption, and it’s backwards. Look at who actually relies on checklists in the real world, and a different pattern shows up: the more consequential the work, the more likely you are to find a checklist behind it, used by people who are unquestionably experts.

Who actually uses them

Airline pilots run a pre-flight checklist before every single flight, regardless of how many thousand hours they’ve logged. Not because they don’t know the steps — because the list of things that can go wrong on a modern aircraft exceeds what any human working memory can reliably hold under pressure, every time, with zero acceptable failure rate. The checklist doesn’t replace the pilot’s skill; it protects that skill from a bad day, a distraction, an interruption mid-sequence.

Surgeons are the case that changed a lot of minds on this, thanks largely to Atul Gawande’s book The Checklist Manifesto. Gawande, a practicing surgeon, documented how a short, deliberately simple pre-surgical checklist — confirm the patient, confirm the site, confirm the antibiotics, confirm the team knows each other’s names and roles — measurably reduced real surgical complications when it was actually followed. Separately, the central-line-infection checklist work led by Dr. Peter Pronovost at Johns Hopkins is one of the most cited examples in patient-safety literature of a simple checklist catching exactly the kind of well-known, individually-obvious step that still gets skipped under real-world time pressure. In both cases, the people using the checklist were highly trained specialists — the checklist wasn’t compensating for a lack of skill, it was compensating for the truth that skill alone doesn’t protect against distraction, fatigue, and complexity.

Engineers and manufacturing teams run the same discipline under different names: control plans, PFMEAs (Process Failure Mode and Effects Analysis), standard work instructions, quality gates. A control plan is, functionally, a checklist — a deliberate, written record of what must be checked, in what order, and why, so that the process doesn’t depend on one person’s memory on one particular day. In my own manufacturing engineering career, the projects that ran cleanly were never the ones where someone especially talented held it all in their head. They were the ones where the critical steps were written down, verified, and followed the same way every time — by the newest tech on the line and the most senior engineer alike.

The real insight, not the surface-level one

The common thread across aviation, surgery, and manufacturing isn’t “these fields are dangerous, so they need extra help.” It’s that complexity has genuinely outgrown what any individual’s memory and judgment can reliably manage alone, every single time, under real conditions — time pressure, interruption, fatigue, multiple things happening at once. A checklist isn’t an admission that you don’t know your job. It’s an acknowledgment that even the best-trained professional is still human, and that a well-built system should be more reliable than any one person’s memory on their worst day.

That reframes what a checklist is for. It’s not a substitute for competence — it’s a tool competent people use specifically because they understand how failure actually happens: not from not knowing the step, but from skipping a known step under real-world pressure.

What makes a checklist actually work (and what doesn’t)

Gawande’s own research is useful here too, because a bad checklist is worse than no checklist — it trains people to stop trusting the list, which defeats the whole purpose. A few practical rules that hold up across every domain above:

• Short, not exhaustive. A checklist that tries to capture everything becomes a document nobody actually reads in the moment. The best ones focus narrowly on the steps that are easy to know and easy to forget under pressure — not a full training manual.
• Built by the people who do the work, not imposed on them. A checklist written by someone who’s never actually done the task tends to miss the real failure points and include irrelevant ones. The aviation and surgical checklists that actually stuck were refined by the pilots and surgeons using them.
• A verification step, not just an instruction step. The strongest checklists don’t just say “do X” — they force a confirmed check: say it out loud, mark it, have a second person verify it. That’s the difference between a checklist and a to-do list.
• Revised when it fails, not defended. Every real checklist in active use has a version history — a near-miss or a real incident that led to a specific added or reworded line. A checklist that’s never been revised has probably never been tested against a real failure.

The takeaway for engineers and managers specifically

If your team’s critical processes live only in the head of your most experienced person, that’s not a sign of strength — it’s a real, unaddressed risk, no matter how good that person is. The fix isn’t a 40-page manual nobody will read. It’s the same discipline Gawande, Pronovost, and every airline captain already rely on: a short, specific, verification-based checklist for the steps that are easy to know and easy to miss — built by the people doing the work, and revised the first time it actually fails.

That’s not a beginner’s tool. It’s what high performers actually use.