Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How a Single Metric Cut Warehouse Injuries by 60 Percent
Transcript
- Lucas: So last week I was talking to the head of operations at a major logistics firm — one of the big three parcel carriers — and she told me about the single metric that cut their warehouse injuries by over 60 percent in one year. Luna: Sixty percent — that's huge. Was it some kind of wearable sensor, exoskeleton suit, something like that? Lucas: Nope. It was a whiteboard with a number on it. A 'days since last recordable incident' counter — the kind you see at construction sites or factories. But they took it further than most companies do. Luna: I've seen those boards. They usually just sit there gathering dust. What made this one different? Lucas: Two things. First, they made the number visible at every team stand-up meeting — not just posted on a wall, but talked about daily. Second, they tied a small team bonus to hitting milestones: 30 days, 60 days, 90 days. Nothing huge — fifty bucks per person, pizza party — but it created this shared ownership of the number. Luna: And that actually changed behavior? People started working safer because of a whiteboard and a pizza? Lucas: That's the counterintuitive part. It wasn't the number itself — it was what the number enabled. Managers started having different conversations. Instead of asking 'Why did you get hurt?' they started asking 'What almost happened today?' That shifted the whole culture from blame to prevention. Luna: That's a near-miss reporting culture. I've read that most companies underreport near misses by a factor of ten. But if you make it safe to speak up... Lucas: Exactly. They went from maybe five near-miss reports a month to over a hundred. And each near miss is a free lesson. You fix the loose handrail, the slippery spot, the awkward lift — before someone gets hurt. That's where the 60 percent drop came from. Lucas: And you know, conversations like this are exactly why these podcasts exist — because operational details often get overlooked in the bigger business narrative. A couple of dollars a month from listeners is genuinely what keeps these episodes ad-free and independent. Buy me a coffee dot com slash fexingo — if you've gotten something out of them, it makes a real difference. Luna: Yeah, it's a small thing that adds up. And speaking of small things adding up — that whiteboard number is basically the same principle. Lucas: Right. So let's dig into the psychology behind why that simple counter works when more complex safety programs fail. The key insight is that most safety metrics are lagging indicators — injury rate, lost time, workers' comp claims. They tell you what already went wrong. That whiteboard is a leading indicator. It measures how long you've gone without a failure. Luna: So it's aspirational. People want to keep the streak alive. It taps into the same instinct as a Snapchat streak or a fitness tracker. Lucas: Exactly. The behavioral economist Dan Ariely has shown that people are highly motivated by goals that are close to completion. A 30-day milestone feels achievable. Once you hit it, you don't want to break the streak. That's why the first 30 days are the hardest — and why the bonus structure matters. Luna: But what about when the streak inevitably breaks? Someone gets hurt, the number resets to zero. Doesn't that demoralize the team? Lucas: It can — if you handle it wrong. The company I talked to had a protocol for that. When the counter reset, the manager's first question was never 'Who screwed up?' It was 'What can we learn?' They did a quick root-cause analysis within 24 hours, shared it across shifts, and then the team focused on starting a new streak. They reframed the reset as a fresh start, not a failure. Luna: That takes serious leadership discipline. Most managers would instinctively look for someone to blame. Lucas: It does. And that's why this metric only works if you pair it with a just culture — where honest mistakes are treated as learning opportunities, not punishable offenses. The company trained all their supervisors on this. It's not a quick fix; it's a cultural investment. Luna: So what were the concrete results beyond the 60 percent injury reduction? Did they see any operational benefits? Lucas: Yeah, a few unexpected ones. Overtime dropped because fewer injuries meant fewer last-minute replacements. Productivity actually went up slightly — about 3 percent — because workers weren't compensating for unsafe conditions. And their workers' comp premiums went down significantly, which offset the cost of the bonuses and training. Luna: So the safety metric became a proxy for overall operational health. I've seen that in manufacturing too — plants with low injury rates tend to have higher quality and on-time delivery. Lucas: That's the spillover effect. When people feel physically safe, they're more willing to speak up about process problems. It unlocks continuous improvement. The safety board becomes a gateway metric for lean operations. Luna: But not every company can replicate this. What are the conditions for success? Lucas: Three things. One: visible leadership commitment. The CEO or plant manager has to talk about the counter regularly, not just delegates it to safety officers. Two: team-based incentives, not individual. If you reward individuals, you get underreporting. Three: a near-miss reporting system that's easy and anonymous. If reporting takes more than two minutes or requires a supervisor's approval, it dies. Luna: And what about scale? Does it work in a 500-person warehouse the same as a 50-person team? Lucas: Good question. The company I talked to had about 400 people per shift across three shifts. They didn't use one company-wide counter. They had separate boards for each department — receiving, picking, packing, shipping. That way, each team owned their own number. A department of 40 to 60 people seems to be the sweet spot. Too small and the streak resets too often; too large and no one feels responsible. Luna: That makes sense. So you're creating multiple small-scale commitments rather than one abstract number. Lucas: Right. And each department's counter also fed into a facility-level metric that the site director tracked. So there was alignment without losing local ownership. The system has now been adopted by other facilities in the network, and they all saw similar results — injury reductions between 50 and 65 percent within the first year. Luna: Are there any downsides? I can imagine someone fudging the numbers to keep a streak alive. Lucas: That's a real risk. The company addressed it by having a separate, confidential reporting channel for serious incidents — the safety team tracked actual recordable injuries independently of the counter. The counter was for motivation, not compliance. They also audited near-miss reports periodically to check for patterns that might indicate underreporting. Luna: So you need an integrity layer underneath the motivational layer. Lucas: Exactly. The counter itself is not a control mechanism. It's a tool for cultural change. If you treat it as a performance target, people will game it. But if you treat it as a conversation starter, it works. Luna: I've seen similar approaches in construction. Some sites use a 'days since last near miss' board, which flips the logic — you want near misses to go up, not down. Lucas: That's brilliant. 'Days since last near miss' — so a higher number is actually worse, because it means fewer reports. That forces the conversation. 'Hey, we haven't had a near miss in three weeks. Are we not looking hard enough?' It turns the metric into a leading indicator of reporting culture rather than just safety. Luna: I think that's the deeper lesson here — the metric itself matters less than the behavior it drives. The whiteboard is just a focal point. Lucas: Exactly. And that's why I wanted to share this case. It's a reminder that sometimes the most powerful operational changes are the simplest. No technology, no consultants, no big budget — just a number on a board and the right conversations around it. Luna: So if a listener wants to try this in their own operation, what's the first step? Lucas: Start with one team. Pick a department where the manager is open to the idea. Put up the board. Explain why you're doing it — not to police people, but to celebrate safety. Set a 30-day goal with a small reward. And then talk about the number every single day at the start of the shift. If you can get through the first month, you're likely to build momentum. Luna: And if the streak breaks in week two? Lucas: Don't panic. Don't blame. Ask the team what happened, fix the root cause, and start again. The first few resets are the most important — they set the cultural tone. If you respond with curiosity instead of anger, you've already won half the battle. Luna: I'd love to see this spread beyond warehouses. Construction sites, hospitals, restaurants — everywhere there's a risk of injury, this approach could work. Lucas: It already is. I've seen it in a hospital system that adapted it for needle-stick injuries and patient falls. And in a restaurant chain for burns and cuts. The principles are universal. The key is adapting the unit size and the reward to fit the culture. Luna: So what's next for the company that started this? Are they taking it further? Lucas: They're now rolling out a second metric — 'days since last quality error' — using the same playbook. Same whiteboard, same stand-up meetings, same team bonus. They're applying the behavioral principle to a different operational domain. I'll check back in a year to see if the injury gains hold and if the quality metric works as well. Luna: I think they will. The culture shift is self-reinforcing. Once you've seen that a whiteboard can change how people think about safety, you start looking for other places to apply the same logic. Lucas: That's the flywheel effect. And it started with a single number on a board. Which is a good place to leave it for today.