The Checklist Manifesto at Work: Why Airline Pilots Make Better Managers Than MBAs

Atul Gawande's The Checklist Manifesto (2009) popularised an insight that applies far beyond medicine: most high-stakes work involves steps that are individually simple but collectively easy to forget or skip under pressure, and the simple discipline of a written checklist dramatically reduces errors. The book is mostly about surgery — where Gawande's research on checklists in the WHO Safe Surgery program reduced complications and deaths substantially — and about aviation, where checklists have been load-bearing safety infrastructure for decades.

The business world has had a mixed relationship with this insight. Consulting firms have built practices around "operational excellence" that incorporate checklist thinking. Some specific areas (software deployment, financial close, legal reviews) have adopted checklists well. Most management, though, has continued to run on memory, instinct, and improvisation, with the occasional dramatic failure that could have been prevented by a one-page document that nobody bothered to write.

The pilots-make-better-managers-than-MBAs claim is deliberately provocative. The underlying point is serious: there's a craft of reliable execution under pressure that airline pilots are specifically trained in and most managers are not. Installing the equivalent in your own management work, through checklists, pays a disproportionate return for the modest setup cost.

What Gawande Actually Found

The WHO Safe Surgery Checklist was deployed in eight hospitals across the world — Toronto, London, Ifakara, Manila, New Delhi, Amman, Seattle, and Auckland. The checklist was simple: 19 items, covering three phases (sign-in before anaesthesia, time-out before incision, sign-out before the patient left the operating room). Things like confirming the patient's identity, the site of the operation, the availability of antibiotics, the expected blood loss.

None of the items were surprising to the surgical teams. They knew these things mattered. The checklist just ensured they happened every time, not just when everyone was paying attention.

The results: surgical deaths dropped by 47%. Major complications dropped by 36%. The effect was measurable in both wealthy and under-resourced hospitals. The intervention was essentially free. The mechanism was not medical expertise — the teams had that — but reliable execution of things they already knew.

Gawande's broader point: in complex professional work, the limit is usually not knowledge but execution under pressure. Experts know more than they can reliably deliver. The checklist is a device for closing the gap between what you know and what you actually do, specifically in moments when your brain is trying to do too many things at once.

Why Most Managers Don't Use Checklists

Three reasons, roughly.

First: checklists look low-status. The associations are factory work, call centres, bureaucratic processes. Senior managers have been told, implicitly, that their judgement is the asset and that formalised processes are for people whose judgement is less trusted. Using a checklist can feel like a demotion from "judgement worker" to "process worker."

This is wrong, and it's wrong in a specific way. Airline captains use checklists. They have extensive judgement and experience; the checklists don't replace judgement, they free it. The captain's cognitive capacity, during the critical moments of takeoff or landing, is for the judgement calls that require human intelligence. The memorisable steps — did we set the flaps, did we confirm the altimeter, did we brief the cabin crew — get delegated to the checklist.

Second: managers often believe their work is too varied for checklists. Every situation is different. You can't list out what needs to happen in every meeting, every decision, every interaction. This is partly true and partly an excuse. A lot of management work is more repetitive than it feels. The specific shapes of repetitive work are where checklists earn their keep.

Third: checklists require discipline. Writing the initial checklist takes thought. Using it, every time, requires you to resist the feeling that this time you don't need it. The discipline is easy to abandon, especially when the checklist hasn't yet saved you from an obvious failure. The value is pre-emptive; its cost is immediate.

The Specific Checklists Worth Building

Not every aspect of management benefits from a checklist. The ones that do share specific properties: they involve steps that matter, that are easy to forget under pressure, that aren't done frequently enough to be fully automatic, and where missing a step has a meaningful cost.

A partial list of management processes where checklists earn their keep:

1. Hiring an executive

A hiring process has perhaps 20-30 steps, spread across weeks, involving multiple interviewers, coordination with candidates, scheduling, reference checks, offer preparation, compensation negotiation, onboarding. Anything that gets forgotten degrades the candidate experience or produces bad hiring decisions.

A hiring checklist for each role covers: role specification, sourcing strategy, interview panel composition, specific questions each interviewer is assigned, reference check plan, compensation bands, onboarding checkpoints. Writing it once, per role type, pays back across multiple hires.

2. Running a major project launch

Product launches, feature releases, campaign launches — anything that involves cross-functional coordination with a specific go-live moment. The failure modes are predictable: marketing didn't know the exact go-live time, legal hadn't reviewed a specific clause, the support team wasn't trained, the metrics dashboard wasn't set up. Each is a simple step that was missed.

A launch checklist, used across launches, catches the systematic omissions. The first version will be imperfect. Every launch, the checklist gets updated with new items you found were missing. Over a year, the checklist becomes a genuine institutional asset.

3. Onboarding a new direct report

The first 90 days of a new direct report's tenure shape their success. What gets covered in the first week, who they should meet, what access they need, what expectations are set, what the development plan looks like. Missing pieces create gaps that are hard to close later.

An onboarding checklist, personalised for each new hire but starting from a standard template, ensures nothing structural is missed. Week-one checklist, thirty-day review template, ninety-day goal-setting framework. Uses the same insight as the surgical checklist: the manager knows what should happen; the checklist ensures it actually does.

4. The end-of-quarter review

Quarter-closes involve specific recurring items: pipeline review, team performance calibration, budget reconciliation, strategic-plan tracking, key-hire pipeline review. Done well, these set up the next quarter. Done poorly — missing items, rushing through — the team enters next quarter with unresolved issues.

A quarterly checklist is the executive version of a surgical checklist. Twenty items, covering every process that should happen at quarter-end. Complete before the quarter ends. The discipline is what separates smooth quarters from chaotic ones.

5. Critical customer meetings

Major customer meetings — QBRs, renewal discussions, escalation conversations — benefit from specific preparation. Pre-meeting: review account history, prep talking points, confirm attendees, establish specific objectives. During meeting: capture decisions, action items, follow-up commitments. Post-meeting: written recap, action execution, scheduled follow-up.

A customer-meeting checklist ensures each meeting is treated with appropriate preparation rather than being winged. The payoff is customer relationships that steadily improve over years, rather than lurching between crises.

How to Build a Checklist That People Will Actually Use

Gawande's research on failed checklists is instructive. Most fail for specific reasons:

• Too long. Beyond roughly 10-15 items, a checklist becomes tedious and gets skipped. Break longer processes into phase-specific checklists.
• Too vague. "Prepare for meeting" is not a checklist item. "Review last three quarterly updates from this account" is.
• Not revised from use. The checklist should evolve. Every time something goes wrong that a checklist item would have prevented, add the item. Every time an item is consistently skipped without consequence, remove it.
• Used as a performance metric. If completion of a checklist is what gets tracked, people will complete it without engaging with it. The value is the specific steps actually being done, not the checklist being ticked.

The working form of a checklist is a one-page document, 10-15 items, specific, living, used privately as a thinking tool rather than a compliance artefact. The discipline is to actually use it, not to create an impressive-looking one.

The Airline Captain Point

Airline captains, by the time they're running commercial flights, have thousands of hours of flight experience. They know what they're doing. They still use checklists for every takeoff and every landing, because the failure modes of forgetting a step — under stress, with many things happening simultaneously — are catastrophic.

Senior management has similar dynamics. You know what you're doing. The failure modes of forgetting a step, under stress and with many things happening, are not usually catastrophic in a single instance, but they're costly in aggregate. The difference between a manager who runs checklists and one who doesn't is not about knowledge. It's about reliable execution of what's already known.

The pilot who refuses to use checklists because she "knows what she's doing" is the pilot you do not want flying your plane. The manager who refuses to use checklists for the same reason is — in a lower-stakes way — making a similar category of error. The checklist is a force multiplier on the judgement you already have, not a substitute for it.