Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How a 30-Second Daily Check Saved a Hospital 2 Million
Transcript
- Lucas: So last week I was reading a JCAHO report — the Joint Commission — and one number jumped out at me. In a major hospital chain, defibrillators were failing readiness checks about 12 percent of the time. That means one in every eight machines, when a code was called, either had a dead battery, missing pads, or some other issue. Luna: That's terrifying. Those are the paddles they use during a cardiac arrest. Lucas: Right. And the hospital chain — I won't name them, but it's one of the top five in the U.S. — they decided to fix it. Not by buying new machines, not by adding a full-time technician. They introduced a single 30-second daily check. That's it. Luna: Thirty seconds? What does that check involve? Lucas: Every morning, the charge nurse in each unit goes to every defib in their area. They open the drawer, confirm the pads are sealed and not expired, press the battery test button, and look for a green light. If it's green, they close it. If it's red or doesn't light up, they flag it for replacement. That's the entire protocol. Luna: And that cut failures by 40 percent? Lucas: Actually more — from 12 percent failure rate down to under 2 percent within six months. The annualized savings were about $2 million, mostly from avoided patient harm lawsuits and not having to rush-rent replacement units. Luna: I'm trying to picture the resistance. Nurses are already slammed. Adding another task — even 30 seconds — that's going to get pushback. Lucas: Absolutely. The first version had a paper log. Nurses had to write down the serial number, the date, the result. That took closer to two minutes, and compliance was maybe 40 percent. So the operations team — this is the smart part — they redesigned the check to be entirely visual. They put a small sticker on the front of the defib cabinet, and the nurse just moves a slider from red to green after the check. No writing. No logging. If the slider is red at end of shift, the next nurse knows it wasn't done. Luna: So it becomes a visual management cue. Like the kanban cards in a factory. Lucas: Exactly. They borrowed from lean manufacturing. The sticker also has a QR code that links to a one-question form — 'Did the defib pass?' — but that's optional. The main thing is the physical slider. Within two weeks, compliance went from 40 percent to 95 percent. Luna: And I assume they also standardized the location of the defibs? Because in some hospitals, the machines get moved around and then nobody knows where they are. Lucas: You're reading ahead. Yes — they mapped every defib location across the hospital and assigned each one a tag number. The daily check is tied to that tag. If a unit borrows a defib from another floor, they have to trade tags so the check still happens. That eliminated the 'it's not my machine' excuse. Luna: It's such a simple intervention. And we see this pattern over and over — the best operational fixes are almost boring. Lucas: Which brings me to something I've been thinking about. These shows we do — they're free, they're ad-free, and they take a fair bit of research to make sure the numbers are right. If you've gotten anything useful out of them, a couple of dollars a month is genuinely what keeps these going. It's at buy me a coffee dot com slash fexingo. Luna: Yeah, it's a small thing that makes a big difference. Like that 30-second check. Lucas: Exactly. So back to the defib story — the hospital didn't stop at the daily check. They also started doing a weekly 'code cart' audit, where they check everything in the crash cart, not just the defib. And they found that the daily check mentality spread to other equipment. Infusion pumps, ventilators — all started getting quick daily lookovers. Luna: So the culture shifted. The daily check became a habit, not a chore. Lucas: Right. And the key insight is that the check is 30 seconds because they deliberately made it too small to skip. If it takes longer, people find reasons not to do it. So the design principle is: make the right thing the easy thing. Luna: How did they measure the savings exactly? Was it just avoided lawsuits? Lucas: They tracked three things. One, the number of 'adverse events' — codes where the defib failed or had a delay. That dropped from about 18 per year to 3. Two, they tracked equipment rental costs. Before, they were renting backup defibs at $200 a day because units didn't trust their own machines. After the check, rentals dropped 80 percent. And three, they estimated the legal liability. A single failed defib lawsuit can settle for $500,000 to $1 million. So avoiding even one or two of those pays for the program many times over. Luna: And the program itself cost almost nothing. Just stickers and some training time. Lucas: Total cost was under $5,000 for stickers, laminated instructions, and a 30-minute training session for charge nurses. So the ROI is essentially infinite. But the real lesson is that you don't need a high-tech solution for a low-tech problem. Luna: I'm thinking about where else this applies. Any operation with expensive, infrequently used equipment — fire extinguishers, backup generators, emergency shutoffs. Lucas: Exactly. In fact, this same hospital chain later applied the daily check to their fire extinguishers — just a quick visual that the pin is in place and the gauge is in the green. That cut extinguisher failure during inspections by 60 percent. And it took 15 seconds. Luna: So the pattern is: identify the single point of failure, design a check that takes under a minute, and make it visual so you can see compliance at a glance. Lucas: Yeah. And one more thing — they also created a 'buddy system' where two units pair up and do a cross-check once a week. That catches the 'I've been doing it wrong' cases. In the first month, they found three units where the nurses thought they were checking the battery, but they were pressing the wrong button. The buddy system fixed that. Luna: So the daily check is the baseline, but the weekly cross-check is the error-correction layer. Lucas: Exactly. And that's the kind of layered operational thinking that turns a 30-second habit into a 40 percent failure reduction. It's not about working harder. It's about designing the work so that the right thing happens automatically. Luna: Alright, I'm going to go check the fire extinguisher in my building. Lucas: Let me know if it's green. I'll be here.