Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How a Hospital Cut ER Wait Times by 40 Percent Using Ops
Transcript
- Lucas: I spent three hours in an emergency room last year with a kid who had a high fever. Not a life-threatening situation, but it was miserable. And the entire time I was sitting there, I kept thinking — there's got to be an operations fix for this. Luna: Yeah, there's actually a really good one. A hospital system in the Midwest cut ER wait times by 40 percent using a set of operational changes that had nothing to do with adding beds or staff. Lucas: That's exactly what I want to dig into. The hospital system was based in Ohio — four hospitals, about 180,000 ER visits a year. They started the pilot in 2018 and within 18 months, average wait times dropped from 187 minutes to 112. That's an hour and fifteen minutes shaved off. Luna: And they didn't just triage differently. They changed the entire flow of the department. Lucas: Right. If today's conversation helps you think about your own operations — whether you're in healthcare or not — the reason this show stays ad-free is listener support. You can find us at buy me a coffee dot com slash fexingo. Just a simple way to keep the content coming. Luna: Agreed. It's a small gesture that makes a big difference for us. Lucas: So the first change they made was to the triage process itself. Most ERs use a five-level system — ESI, the Emergency Severity Index — where a nurse assigns a level from 1 to 5. Level 1 is cardiac arrest, level 5 is a stubbed toe. The problem is, level 3 covers a huge range: chest pain, abdominal pain, fractures, infections. That's where the variability lives. Luna: So they created a sub-triage for level 3 patients? Lucas: Exactly. They developed a secondary algorithm that looked at three things: predicted resource need — how many tests, IVs, imaging studies — predicted bed type — does this person need a critical care bed, a monitored bed, or a regular gurney — and expected length of stay. They used historical data to train the model. It took maybe 30 seconds extra at registration. Luna: And that alone reduced the bottleneck at the physician's door? Lucas: Yes, because now when a doctor picked up a chart, they knew whether the patient needed a full workup or could be discharged with a prescription. But the bigger win was the next piece: real-time bed tracking. Before this, when a bed opened up, it took an average of 22 minutes for housekeeping to clean it and for the charge nurse to assign it. That's 22 minutes of wasted capacity. Luna: So they built a dashboard. Lucas: They used a simple digital whiteboard. Every bed had a status — occupied, dirty, being cleaned, clean available. The housekeeping team got notifications on handheld devices. The moment a bed was vacated, the timer started. If a bed was dirty for more than 15 minutes, a supervisor got an alert. Within three months, average turnover time dropped to nine minutes. Luna: That's a classic operations move — measure the process step, set a target, close the feedback loop. Lucas: Exactly. And the third piece was the most interesting. They implemented a pull system for lab results. In most hospitals, when a doctor orders lab work, the phlebotomist draws the blood, it gets sent to the lab, and the lab processes it in a batch. That batch processing creates variability — some patients wait 20 minutes, some wait 90. Luna: So they flipped it to a continuous flow? Lucas: Not quite continuous, but they prioritized based on the patient's location. If the patient was in the ER, the lab had a dedicated 'STAT' line. They pulled the sample from the pneumatic tube system within two minutes of arrival. The result was that ER lab turnaround time dropped from 47 minutes to 19 minutes on average. Luna: And that directly reduced wait time because doctors could make decisions faster. Lucas: Right. But here's the thing — none of these changes are technically complex. What made them work was the measurement and the accountability. They tracked three metrics daily: door to provider time, lab turnaround time, and bed turnover time. Every morning, the charge nurse reviewed the prior day's numbers with the team. If a metric was off, they talked about what went wrong and what they'd change. Luna: That's the culture piece. Most operations failures aren't about not knowing what to do — they're about not doing it consistently. Lucas: Exactly. And the results were dramatic enough that the system expanded the protocol to all four hospitals within two years. They also saw a secondary effect: patient satisfaction scores went up by 18 points, and the number of patients who left without being seen dropped from 5 percent to under 2 percent. Luna: That last metric is huge — patients leaving without being seen is both a safety risk and a revenue loss. Lucas: Huge. And it's a reminder that operations improvements often compound. You fix one bottleneck, and the downstream effects show up in places you didn't expect. The lab change alone probably saved dozens of patients from leaving, because they got results quickly and were discharged sooner. Luna: So what's the lesson for someone outside healthcare? If I run a small business, a restaurant, a logistics company — what do I take away? Lucas: Three things. One: measure the handoffs, not just the final outcome. ER wait time is the final outcome, but the real leverage is in the sub-processes — triage, bed turnover, lab turnaround. Two: set a specific, numerical target for each sub-process. Not 'faster', but 'under 15 minutes'. Three: create a daily feedback loop. Someone reviews the numbers and talks about what to do differently. Luna: And none of that requires software. A whiteboard and a stopwatch can get you most of the way. Lucas: Honestly, I think that's the most underrated tool in operations. The hospital system I mentioned didn't buy any new technology. They used the existing electronic health record, plus a digital whiteboard that was essentially a shared spreadsheet. The hard part was getting people to follow the new process. Luna: And sustaining it. I've seen operations initiatives that work for three months and then fall apart. Lucas: Yeah, that's the real challenge. The hospital kept it going by embedding the metrics into the charge nurse's daily stand-up meeting. They also ran a quarterly review where they looked at trends. If a metric started slipping, they'd investigate. That kind of discipline is rare. Luna: So if someone listening wants to try this in their own operation, where do they start? Lucas: Pick one bottleneck. Don't try to fix everything at once. For the hospital, the biggest bottleneck was actually the triage process. They fixed that, then moved to bed turnover, then lab turnaround. Each change took about three months to implement and stabilize. That's a 12-month program for a 40 percent improvement. Not bad. Luna: And they could have done it in six months if they'd thrown more resources at it, but they chose a sustainable pace. Lucas: Exactly. And that's the other lesson. Operations improvement is a marathon, not a sprint. The hospital's CEO said in an interview that the biggest mistake they made initially was trying to change everything at once. They had to pull back and sequence it. Luna: So the takeaway is: pick one metric, set a target, measure daily, and don't stop until you hit it. Then move to the next. Lucas: That's the playbook. And it works whether you're running an ER, a warehouse, or a call center. The specifics change, but the logic is the same. Luna: Alright, next episode we'll look at a case where the opposite happened — a company that tried to optimize everything and ended up making things worse. Lucas: I can think of a few candidates. Let's dig into that next time.