Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How the Navy Invented the Nuclear Checklist
Transcript
- Lucas: So there's this moment in the history of operations that I think about a lot. The year is 1952. The United States Navy is building its first nuclear-powered submarine, the USS Nautilus. And the man in charge — Admiral Hyman Rickover — has a problem. His engineers are brilliant, but they're making small mistakes. A valve left open here, a gauge misread there. Nothing fatal yet, but in a nuclear reactor, a small mistake can kill everyone on board. Luna: And this is before checklists were common, right? I mean, pilots had pre-flight checklists, but that was still relatively new. Lucas: Exactly. The idea of a checklist in an industrial setting was almost unheard of. The Navy had procedures, sure, but they were written in thick manuals that nobody actually referenced during operations. Rickover realized that the human brain, no matter how well-trained, will skip steps under pressure. So he introduced a simple thing: a laminated card with a step-by-step sequence for every critical procedure in the reactor control room. Luna: And this was the birth of the modern operations checklist. Not in a hospital, not in an airline cockpit, but in a submarine. Lucas: Right. And it spread fast. The Navy required every nuclear submarine to use checklists for reactor startups, shutdowns, and emergency drills. By the late 1950s, the accident rate in nuclear propulsion dropped by something like 70 percent. That's a huge number. And Rickover didn't just mandate checklists — he enforced them. He would personally inspect submarine crews and if someone skipped a step, they were out. Luna: That's intense. But it makes sense. If you're going to trust a crew with a nuclear reactor, you want zero tolerance for deviation. Lucas: Precisely. Now fast forward a few decades. The idea migrates to commercial aviation in a big way. In the 1970s, after a series of crashes, airlines adopted the cockpit checklist as standard. Then in the 2000s, Dr. Atul Gawande popularized the surgical checklist in his book 'The Checklist Manifesto.' But the origin — the real proof of concept — was Rickover's nuclear submarine program. Luna: So the question for our listeners is: how can a small business apply this? Not everyone runs a nuclear reactor, but everyone makes costly errors. Lucas: Exactly. So let's drill into one concrete case. A mid-sized manufacturing company — let's call them Precision Parts — had a problem with equipment failures. Their machines would overheat or misalign, costing them about $500,000 a year in downtime. They brought in an operations consultant who basically said: 'You need a pre-start checklist for every machine.' Luna: And did it work? Lucas: Within six months, equipment failures dropped by 70 percent. The checklist forced operators to check oil levels, belt tension, coolant temperature — things they knew to do but would forget when they were rushing. The key was that the checklist was short — ten items — and laminated. Operators had to sign off after each check. Luna: So the principle is the same as Rickover's: standardize the routine so the brain doesn't have to remember every step under pressure. Lucas: Exactly. And it's not just manufacturing. You see it in software deployments — companies like Google and Amazon use playbooks that are essentially checklists for launching code. A missing step in a deployment can take down the entire site. Luna: But checklists can also fail, right? I remember reading about a hospital where the checklist became a box-ticking exercise and actually didn't reduce infections. Lucas: Great point. That's the dark side of checklists. In 2010, a study in the New England Journal of Medicine found that in some hospitals, the surgical checklist didn't improve outcomes. Why? Because the culture didn't change. Nurses felt intimidated to speak up if a surgeon skipped a step. The checklist was just a piece of paper, not a tool for teamwork. Luna: So the effectiveness depends on the culture around it. Rickover didn't just hand out cards — he drilled accountability. Lucas: Right. And that's the lesson for any business. If you implement a checklist but nobody feels empowered to enforce it, you're wasting your time. You need leadership that says: 'This step is non-negotiable.' And that starts at the top. Luna: Speaking of non-negotiable, I want to circle back to something we touched on earlier. The idea that small, consistent practices — like a checklist — can have an outsized impact. It reminds me of how listener support works for shows like ours. Lucas: Yeah, it's a good parallel. A few dollars a month from people who find value in what we do — that's the thing that keeps these conversations going. We don't run ads, we don't have sponsors, so it's genuinely listener-driven. If these episodes have helped you think differently about your own operations, buy me a coffee dot com slash fexingo is the simplest way to keep it ad-free. Luna: And like a checklist, it's a small step that adds up. Even a couple of bucks makes a real difference. But back to the topic — I want to talk about a checklist failure that almost caused a nuclear disaster. Lucas: Oh, this is good. In 1961, a nuclear submarine called the USS Sargo had a reactor accident during a test. The crew followed the checklist, but the checklist itself had an error. It instructed them to open a valve that should have remained closed. That mistake led to a coolant leak and a partial meltdown. Luna: So the checklist was wrong. That's a whole other layer — the quality of the checklist itself. Lucas: Exactly. Rickover's response was to create a rigorous validation process. Every new checklist had to be reviewed by at least three different engineers, then tested in a simulator with a crew who had never seen it. If they made a mistake, they revised the checklist. That's how you build a reliable tool. Luna: So for a business, it's not enough to just write a checklist. You have to test it, iterate, and make sure it's actually correct. Lucas: Right. And you need to update it as conditions change. One of the reasons the airline checklist is so effective is that it's revised after every incident. The National Transportation Safety Board issues recommendations, and the checklist gets updated. Same should happen in any business. Luna: So takeaway: start with one critical process, write a short checklist, test it with your team, and enforce it. But also be willing to revise it. Lucas: And remember: the goal isn't to eliminate human judgment. It's to free up mental bandwidth for the things that actually require thinking. When you don't have to remember the routine, you can focus on the unusual. That's the real power of a good checklist. Luna: Alright, I'm going to go write a checklist for my morning routine. But seriously, thanks for digging into this history. Lucas: Glad to. Next time, we'll look at another operations tool that came from an unexpected place — the military's use of after-action reviews. That's a whole other story.