Latest / The Operations Podcast with Fexingo: Process, People, and Profit in Modern Business / How A Hospital Chain Cut Supply Waste By Forty Percent
Transcript
- Lucas: Let’s talk about the hidden economy inside a hospital operating room. Most people think of surgery as purely medical skill, but it’s also a high-stakes logistical operation. And for decades, that logistics side has been bleeding money through expired supplies, misfiled instruments, and reactive ordering. Luna: Right, because when you’re in a crisis, you don’t want to wait for a procurement email. You grab what’s there. But that habit creates massive waste over time. Lucas: Exactly. It’s the classic push system problem. Supplies are ordered based on historical averages rather than actual usage, leading to either stockouts during emergencies or mountains of unused, expiring goods sitting on shelves. One mid-sized hospital network I’ve been tracking recently managed to cut their supply waste by forty percent in just eighteen months. That isn’t a theoretical model; they actually did it. Luna: Forty percent is huge for margins in healthcare. What was the lever they pulled? Was it renegotiating contracts with vendors? Lucas: Surprisingly, no. Their vendor contracts stayed mostly static. The change was internal, specifically in how they managed their sterile processing departments and surgical carts. They stopped treating inventory like a warehouse problem and started treating it like a visual management challenge. They installed simple, color-coded tracking systems directly at the point of use. Luna: So, instead of central warehouses sending out bulk orders, they let the surgical teams signal when they needed replenishment? Lucas: Precisely. It’s a pull system. If a surgeon opens three sutures, the system registers three sutures gone. It triggers a restock only for those three items, not a full box. This eliminated the guesswork. But here is where it gets interesting: the technology was secondary. The real battle was cultural. Luna: I can imagine. Nurses and surgeons are busy. Adding scanning or tracking steps sounds like bureaucracy before it sounds like efficiency. Lucas: That was the initial resistance. Staff felt monitored, like they were being clocked for every suture clip. The leadership team had to pivot the narrative entirely. They didn’t frame it as cost-cutting; they framed it as safety and reliability. They showed data proving that the old system caused frequent delays because critical items were expired or missing. The new system meant reliable availability. Luna: Oh, I like that. Reframing waste reduction as patient safety assurance is a much stronger motivator for clinical staff. Lucas: It changed the behavior overnight. Once nurses saw that their preferred instruments were always ready because the system tracked them accurately, adoption spiked. They became champions of the process. But there was one snag with the financial reporting. Luna: What kind of snag? Did the savings show up immediately on the balance sheet? Lucas: Not immediately. Because healthcare accounting lags, the waste appeared as an expense only when items expired. So cutting waste meant fewer write-offs, but it took six months for the P&L to reflect the improvement. Leadership had to convince the board to keep funding the initiative even though the immediate cash flow impact wasn't obvious yet. Luna: That’s a tough sell. Convincing executives to invest in something that saves money but doesn’t generate revenue right away requires a lot of patience. Lucas: They used a proxy metric: capital availability. They argued that reducing tied-up inventory would free up cash to buy new imaging technology. That resonated. The board approved the next phase of investment because it was linked to tangible equipment upgrades, not just abstract efficiency gains. Luna: Smart. Using the operational win to fund the strategic purchase creates a self-reinforcing cycle. Okay, so we have the process, the culture shift, and the financial framing. But how do you maintain this? Processes tend to drift back to old habits once the initial excitement fades. Lucas: They embedded the metrics into daily huddles. Not high-level quarterly reviews, but ten-minute morning briefings with charge nurses and supply chain managers. They looked at one number: fill rate for critical trays. If it dipped below ninety-eight percent, they investigated immediately. It kept the system tight. Luna: Simple, visible, and actionable. It prevents the slow creep of inefficiency that usually kills these projects. Lucas: Absolutely. And it empowers frontline staff. When a nurse sees the fill rate drop, she knows something is wrong with the restocking process, not necessarily her own work. It shifts accountability to the system design. Luna: I love that distinction. System accountability versus individual blame. That’s key for psychological safety in any high-risk environment. Lucas: Right. If you blame the nurse for a missing item, she’ll hide errors. If you blame the process, she’ll help fix it. This hospital realized that their waste wasn’t just money; it was trust erosion. Fixing the process rebuilt trust between operations and clinical teams. Luna: It’s fascinating how operational fixes often turn out to be relationship fixes. Does this model scale beyond hospitals? Lucas: It scales anywhere with complex inventory and high stakes. Think automotive assembly lines or even high-end manufacturing. The principle holds: make the invisible visible, and let the users drive the replenishment signal. Luna: Yeah, the Toyota Production System roots are showing here. Pull-based systems aren’t new, but applying them to sterile processing feels novel enough to be impactful. Lucas: It’s not the concept that’s new; it’s the execution detail. Most places try to automate the pull signal with expensive software before fixing the physical workflow. This hospital started with colored tags and whiteboards before adding RFID scanners. Simple first, tech second. Luna: Classic lean wisdom. Don’t put a digital bandage on a broken physical process. Have you seen other industries struggle with this same sequence? Lucas: Retail does it all the time. They launch a fancy app for inventory tracking while the shelf stocking process remains chaotic. The data becomes garbage because the physical reality hasn’t aligned with the digital record. Luna: Garbage in, garbage out. It reminds me of how some companies implement CRM tools without cleaning their customer data first. Same pattern. Lucas: Exactly. The tool amplifies whatever process precedes it. If the process is flawed, the tool just makes failure faster. Luna: So the lesson is: stabilize the physical flow, then digitize the signal. Got it. Lucas: Before we dive deeper into the specific metrics they used to track fill rates, I want to mention something real about how this show exists. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that’s literally what funds making this many of these conversations happen without ads interrupting your commute. Luna: Yeah, it’s cool to know that the ad-free experience is directly supported by people who value deep-dive operations analysis like this. Lucas: It keeps us independent. We can follow the data wherever it leads, even if it challenges conventional wisdom. Anyway, back to those metrics. How did they define 'fill rate' precisely? Luna: Was it just whether the tray was available, or did they measure something more granular like preparation time? Lucas: They measured two things. First, availability: was the correct instrument set present within five minutes of the call? Second, accuracy: was it the set? Mis-picks are a huge source of delay. They tracked both separately. Luna: Interesting. Availability without accuracy is dangerous in surgery. You don’t want a tray fast if it’s missing the scalpel. Lucas: Right. So they weighted accuracy higher in their scorecards. If accuracy dropped, they paused availability bonuses until the root cause was fixed. It prevented speed from shame scenarios. Luna: That’s a nuanced incentive structure. Most places just reward speed and ignore errors until they become catastrophic. Lucas: Exactly. This hospital understood that in sterile processing, error prevention is the primary driver of speed. Fewer errors mean less re-work, which means faster throughput. Luna: So efficiency comes from quality, not just hustle. That flips the usual manufacturing script on its head. Lucas: It does. And it validates the initial cultural investment. When staff feel safe reporting near-misses, the system learns faster. It becomes a learning organization, not just a compliant one. Luna: I wonder if this approach could work in smaller clinics too, or if the volume required to justify the tracking infrastructure is too high. Lucas: Actually, smaller clinics benefit more proportionally. Their overhead is tighter. Losing two percent of inventory hurts them more than a large network. The visual management tools are cheap—whiteboards and colored tape cost almost nothing. Luna: So the barrier isn’t cost; it’s the willingness to change routine. Which is always the hardest part. Lucas: Always. The technology is easy. The human behavior is hard. But when you align the tool with the user’s goal—getting the job done safely—it becomes much easier. Luna: It’s a reminder that operations isn’t just about machines; it’s about designing environments where good decisions are the default decisions. Lucas: Spot on. If we look at the broader market today, in September twenty twenty-six, we’re seeing more sectors realize that resilience comes from visibility, not just redundancy. Do you think we’ll see this pull-system logic expand into service industries beyond healthcare? Luna: Definitely. Hospitality and professional services already struggle with resource allocation. Making capacity visible and pull-driven could transform client satisfaction. Lucas: I think so too. The next frontier might be knowledge work. Tracking document access and tool usage to optimize workflows. It’s a long way from sterile trays, but the underlying principle of visualizing flow remains the same. Luna: From surgical kits to code repositories. The language changes, but the need for clear signals doesn’t. Lucas: Exactly. It’s all about reducing noise so the important signals get through.