Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Rail Yard Cut Wait Times 80 Percent With One App
Transcript
- Lucas: So there's this freight rail yard in the Midwest, moves about two thousand cars a day, and last year they got locomotive turnaround time down from ninety minutes to under eighteen. Eighty percent cut. Luna: Eighty percent? That's not a tweak, that's a transformation. What was the secret? Lucas: A single mobile app, believe it or not. Not a new engine, not more track, not a bigger crew. One app on a rugged tablet that replaced the radio back and forth between the yard master, the mechanical crew, and the train crew. Luna: So the bottleneck was communication, not machinery. Lucas: Exactly. The physical work of inspecting the locomotive, refueling it, checking the brakes — that was already tight. The killer was the coordination. Every step required a radio call, a wait for a response, sometimes a repeat because the guy was inside the cab or the noise drowned it out. The yard master had a whiteboard, but it was always out of date. Luna: And the app just replaced the radio? Seems almost too simple. Lucas: Not just replaced it. The app forced a sequence. Each task had to be checked off in order before the next one could start. So the fuel crew couldn't mark done until the mechanical inspection was signed off. The system enforced the workflow that the whiteboard only suggested. Luna: The old system relied on memory and trust. The app made it structural. Lucas: Right. And that structural change had a side effect: the data started accumulating. For the first time they knew exactly how long each step took, where the delays actually built, and who was waiting on whom. That's where the real gains came from — not the app itself, but the visibility it created. Luna: What was the first bottleneck they found once they had the data? Lucas: It was the brake test. Every locomotive has to have its brakes tested before it moves, and that test required a certified inspector who was often on the other side of the yard. The crew would finish fueling, call for the inspector, and then sit there for twenty minutes. The app didn't solve that instantly, but it made the delay obvious, so they re-routed one inspector to be closer to the fueling pad, and that alone cut ten minutes. Luna: So the app was a catalyst for a physical change. Lucas: Exactly. And the financials are almost funny. The app itself cost less than thirty thousand dollars to build on an off-the-shelf platform. The inspector re-routing cost nothing. The yard now turns around a locomotive in the time it used to take just to get the radio call answered. Luna: I bet the crews didn't just embrace it overnight. Lucas: Oh, they hated it at first. The veteran crews had done it their way for twenty years. They didn't want to tap a screen after every step, especially in the middle of a snowy night. The yard master told me the first week, he had four guys threaten to quit. Luna: So how did they turn that around? How did they get buy-in? Lucas: This is the part I love. They didn't force it. They brought in a retired dispatcher, a guy named Ray who had worked the yard for thirty years and was respected by everyone. He shadowed the crews for two weeks, not to police them but to understand their objections, then he sat with each shift and showed them the data. He'd say, look, you told me you're waiting on the fuel crew, but the app says the fuel crew finished nine minutes ago. The data was hard to argue with. Luna: So it wasn't about trusting the app, it was about trusting Ray — and the data he brought. Lucas: Exactly. Within a month, the same guys who threatened to quit were the ones reminding each other to hit the button. The app became a source of pride, because they were hitting turnaround times nobody thought possible. Luna: And that kind of peer pressure is a lot more effective than a mandate from above. Lucas: It's the whole story of operational change in a nutshell. The innovation wasn't the app, it was the respect Ray brought to that conversation. But the app was what made respect possible, because it gave them a shared source of truth. Luna: You know, this reminds me of something from our own show. We spend every episode digging into these small operational fixes, and I think the reason we keep finding the same pattern is that the hardest part is rarely the fix itself — it's getting people to see the problem. Lucas: You're absolutely right. And it's the reason we do this show, honestly. These conversations, they change how we think about our own work, and I hope they do the same for our listeners. If this show has ever helped you look at a bottleneck differently, or given you an idea you actually used, that's the whole win. And if you ever feel like supporting what we do here, you can buy us a coffee at buy me a coffee dot com slash fexingo. No pressure, but every bit helps keep this show ad-free. Luna: It really does, and we appreciate it. But back to the yard — what was the on-time performance before and after? Lucas: That's the kicker. They went from seventy-two percent on-time departures to ninety-four percent, and they did it without adding a single locomotive. The app didn't just save time, it smoothed the whole schedule. When a locomotive is ready when it's supposed to be, the entire yard breathes easier. Luna: It's like the airline boarding example we did a while back — the fix seemed so small, but the ripple effects were huge. Lucas: Exactly. And what's interesting is the cost. This whole project was under fifty thousand dollars, including the tablets. A new yard switcher costs two million. That's the kind of ROI that makes CFOs sit up. Luna: But you said the app didn't fix everything overnight. What were the unexpected snags? Lucas: The biggest one was battery life. The tablets kept dying in the cold weather, so they had to buy ruggedized cases with extended batteries. That cost an extra twelve hundred dollars per device. But that was a minor blip compared to the cultural shift. Luna: What about the yard master's whiteboard? Did they keep it as a backup? Lucas: They actually kept it for the first two months as a safety net, but it became a symbol of the old way. By the third month, they stopped updating it, and then they physically took it down. The crews said it felt like a graduation. Luna: That's a nice image. Let's talk about measurement — how did they verify the eighty percent? Did they trust the app's data? Lucas: They ran a parallel study for two weeks. A summer intern manually recorded timestamps on a clipboard for every step of a dozen turnarounds. The app data matched within a minute on average. That gave the finance team confidence to declare the win. Luna: So they validated the system with old-school observation. Lucas: That's the discipline you need. And it's worth saying that the eighty percent is the headline, but the real gift was the data trail. They now know how long every step takes in every weather condition, and they use that to plan crew shifts and maintenance windows. Luna: Could this work in a warehouse or a hospital? Is the pattern transferable? Lucas: Very much so. The pattern is: pick a process that has a clear start and end, identify where the handoffs happen, and ask if the information flows as fast as the physical work. In most places, information lags behind. A shared digital checklist is the cheapest way to close that gap. Luna: What would you say is the one thing a listener could take away and apply tomorrow? Lucas: Map the handoffs. Draw a simple flowchart of your turnaround process, no matter what it is — a repair, a patient discharge, a shipment. Wherever there's a verbal or paper relay, that's your candidate. The fix may not be an app, but it will be something that makes the status visible to everyone at once. Luna: Visibility over vanity. That's a good note to end on. Lucas: I think that's the whole manual, right there. Next time we'll look at how a small bakery cut its order errors thirty percent with a one-word change on the counter ticket — but that's a story for another day.