Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How a Single Checklist Saves Airlines Millions
Transcript
- Lucas: So, Luna, I want to talk about something that sounds almost too simple to be worth a whole episode: the checklist. Luna: The checklist? Like, a grocery list, but for business? Lucas: Exactly that. But the story behind it is wild. It starts with a crash. October 30, 1935, at Wright Airfield in Dayton, Ohio. The Boeing Model 299 — the prototype for what would become the B-17 Flying Fortress — takes off, climbs to about 300 feet, stalls, and crashes in a fireball. Two of the five crew die, including the pilot, Major Ployer Hill. Luna: I've heard of that crash. The investigation blamed pilot error, right? Lucas: Right. But the thing is, the Model 299 was a huge leap in complexity. It had four engines, retractable landing gear, wing flaps, a complex electrical system — things the pilots had never managed simultaneously. The pilot forgot to release the elevator gust lock before takeoff. That's it. A single missed step. Luna: So the solution was... a checklist? Lucas: Yes. The Army Air Corps convened a panel of test pilots, and they decided that even the best pilots couldn't reliably remember every step under pressure. So they wrote a simple checklist — takeoff, flight, landing — with each step in order. From that point on, the B-17 flew 1.8 million miles without a single accident attributable to pilot error. Luna: That's a massive improvement. But it's almost embarrassing, isn't it? That a checklist — something so basic — could prevent something so catastrophic. Lucas: Embarrassing, but true. And it's not just aviation. The checklist has become a cornerstone of operational excellence in industries where the stakes are high. Surgery, for example. In 2008, Atul Gawande, a surgeon and writer, published a study in the New England Journal of Medicine about a nineteen-item surgical checklist. Eight hospitals around the world adopted it. The result? Major complications dropped by 36 percent, and deaths dropped by 47 percent. Luna: Forty-seven percent fewer deaths. That's staggering. And it's just a list of things like 'confirm patient identity' and 'count sponges'? Lucas: Exactly. The checklist didn't teach surgeons anything new. It just made sure they didn't skip the basics. Gawande later wrote a whole book about it, The Checklist Manifesto. He argues that in complex environments, the volume and complexity of knowledge has exceeded our individual ability to remember and apply it correctly. The checklist is a cognitive safety net. Luna: So where else has this been applied? I'm thinking construction, for instance. Lucas: Construction is a great example. The Burj Khalifa, the tallest building in the world, was built using an extensive system of checklists for every critical step — concrete pouring, steel erection, safety protocols. The project had zero structural failures. In software, too. Google's Site Reliability Engineering team uses 'playbooks' — which are basically checklists — for incident response. When the system goes down, the on-call engineer doesn't think from scratch. They follow a step-by-step runbook. Luna: And that speeds up recovery and reduces mistakes under pressure. Lucas: Exactly. A study from the University of Texas found that airline crews using checklists reduced errors by over 50 percent. In the operating room, compliance with basic safety steps went from around 60 percent to over 90 percent after checklists were introduced. The numbers are consistent across domains. Luna: Okay, so if checklists are so effective, why doesn't everyone use them? Why do we see so many preventable errors in business? Lucas: Partly ego. Skilled professionals, especially experts, often resist checklists because they think they don't need them. There's a perception that using a checklist is a sign of incompetence. But the data shows the opposite: the most skilled pilots and surgeons are often the most enthusiastic checklist users. They know their memory isn't infallible. Luna: That's a good point. It's about humility. Lucas: Right. And there's also the issue of bad checklists. A poorly designed checklist — too long, too vague, too context-insensitive — becomes just another form to fill out. The key is designing checklists that are short, precise, and tested by the people who will use them. Gawande's surgical checklist was only nineteen items, which took about two minutes to complete. Luna: Two minutes to potentially save a life. That seems like a no-brainer. But in business, we have meetings about meetings. Maybe we need more checklists and fewer meetings. Lucas: Honestly, that's not a bad idea. There's a reason the checklist has stuck around for 90 years. It's the simplest form of operational discipline. And today, as we're recording this in early June 2026, with so many companies trying to adopt AI and automation, sometimes the most powerful tool is still a piece of paper with ten steps. Luna: Speaking of which, if you found value in this conversation — maybe it moved your thinking forward in some small way — you can support the show at buy me a coffee dot com slash fexingo. It's a simple way to keep us ad-free and focused on content like this. Lucas: Yeah, we really appreciate that. And it genuinely helps us keep the lights on. Now, back to checklists — one more example I love is from the book 'The Checklist Manifesto' itself. Gawande describes how a checklist for building a skyscraper in New York prevented a massive concrete pour error that could have cost millions. The checklist simply required a supervisor to verify that the concrete mix matched the specification before pouring. One step, but it caught a discrepancy that would have weakened the entire foundation. Luna: So it's not just about preventing errors; it's about enabling coordination. When you have multiple teams — pilots, ground crew, air traffic control — the checklist ensures everyone is on the same page. Lucas: Exactly. The checklist acts as a communication tool. In the cockpit, the captain reads the checklist item, and the first officer responds. That verbal confirmation ensures both are aware. In surgery, the entire team pauses for a 'time-out' before the incision to confirm patient, procedure, and site. It's a ritual that aligns the team. Luna: I'm wondering, has there been a case where a checklist backfired? Where it caused more harm than good? Lucas: There are cases where checklists become bureaucratic — people fill them out mindlessly, checking boxes without actually thinking. That's a real danger. In the 1990s, the US Navy had a checklist for nuclear submarine maintenance that was so long and detailed that sailors started skipping steps or falsifying signatures. The solution wasn't to abandon checklists, but to redesign them: shorter, with meaningful items, and with random audits to ensure compliance. Luna: So the checklist itself needs a checklist. Make sure it's used correctly. Lucas: Right. And that's a good lesson for any operational tool: you have to manage the tool, not just deploy it. But when done right, the return on investment is enormous. The cost of designing a checklist is minimal. The cost of a single error can be millions of dollars or — in aviation or medicine — lives. Luna: Let's bring it back to business execution. How can a small business owner or a team lead apply this today? Lucas: I'd say start with your most critical, error-prone process. Maybe it's onboarding a new employee, or deploying software, or handling a customer complaint. Write down every step that must happen. Then test it with someone who hasn't done it before. You'll find missing steps almost immediately. Then iterate. Keep it to five to ten items per checklist, and review it quarterly. Luna: And don't forget the team involvement. If the people doing the work design the checklist, they'll actually use it. Lucas: Exactly. That was a key insight from the aviation industry — the checklists were created by the pilots who would fly the plane. They knew what was important and what could be skipped. When you impose a checklist from above, it often fails. Luna: So the humble checklist: it's a tool for discipline, coordination, and humility. And it's been around longer than most of the technology we talk about on this show. Lucas: And it still works. That's the beauty of it. Sometimes the most effective operational improvement isn't a new algorithm or a machine learning model. It's a list of things you already know you should do, written down so you don't forget. Luna: I think I'm going to make a checklist for my morning routine. No more forgetting my keys. Lucas: There you go. Start with the small stuff. Who knows — you might end up saving a life someday.