Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Fast-Food Chain Cut Drive-Thru Wait Times 28 Percent With One Change
Transcript
- Lucas: So there's this fast-food chain — I'm not going to name them, but they operate about a thousand locations in the US — and last year they cut their average drive-thru wait time from three minutes and forty-two seconds down to two minutes and thirty-eight seconds. Luna: That's a twenty-eight percent drop. And I'm guessing they didn't add a second drive-thru lane or double the kitchen staff. Lucas: Correct. They did one thing: they changed when the order-taker starts entering the order into the system. That's it. Luna: Okay, I'm intrigued. Because when I go through a drive-thru, the bottleneck always seems to be the kitchen, not the person at the speaker. Lucas: Right — that's what everyone assumes. But what they found, after they put sensors on every step of the process, was that the real bottleneck was a tiny gap between taking the order and sending it to the kitchen. The order-taker would wait until the customer finished speaking, then they'd type it in. That pause — the time to listen, process, then type — was averaging about eighteen seconds per order. Luna: And in a chain with high volume, those seconds add up fast. Lucas: Exactly. So the fix came from watching how the best-performing stores operated. In the top-decile locations, order-takers were entering the order while the customer was still speaking — they'd type the first item as the customer said it, then the next item, and so on. They weren't waiting for the full order to land before they started typing. Luna: That's interesting — but doesn't that risk more errors? If I'm typing while you're still talking, I might miss something or mistype because I'm splitting my attention. Lucas: That's exactly what the company was worried about. Their initial assumption was that accuracy would suffer. So they ran a controlled test in thirty stores. And what they found was that error rates actually went down slightly — about two percent. Because the order-taker could ask clarifying questions in the moment rather than trying to remember everything the customer said. Luna: So it's not just about typing faster — it's about reducing the cognitive load of holding the order in short-term memory. Lucas: Precisely. And the timing improvement came from eliminating that eighteen-second dead zone. Across a peak lunch hour, that adds up to about seven minutes per hour of extra capacity at the speaker. Which means fewer cars backing up onto the street. Luna: I'd love to hear how this connects to the operations stuff we've talked about in other episodes — like the hospital ER board or the Toyota andon system. Lucas: Yeah, it's actually a textbook application of what the lean manufacturing folks call 'pull' — the kitchen only starts making the order once it's fully entered, so the order-taker is essentially the pace-setter. And the fix is a version of 'jidoka' — building quality in at the source by catching issues earlier. Luna: Before we go deeper — if today's episode gave you a useful lens or a practical idea you might try, the reason these conversations stay completely ad-free is listener support. People who find real value here can toss something into the tip jar at buy me a coffee dot com slash fexingo. No pressure, no perks — just a way to keep the show independent and focused on stuff that actually moves the needle. Lucas: Yeah, and if you're a regular listener, you know we don't do sponsor reads or interrupt the flow with ads. It's entirely funded by people who get something out of it. That's it — now back to the drive-thru. Luna: So once they implemented this change system-wide, how did they train order-takers to break the habit of waiting? Lucas: They used what they called 'shadowing' — new hires would spend two shifts listening to a veteran order-taker who was already doing the simultaneous-entry technique. Then they'd switch roles. The key was that they didn't just tell people to type faster — they showed them the specific rhythm: type the first item while the customer pauses between items, then confirm it visually before moving on. Luna: And they didn't add any new hardware? No dual screens or voice recognition? Lucas: Zero new hardware. Same headsets, same point of sale terminals. The only cost was about thirty minutes of training per employee. And the company estimated that the reduction in wait times led to a roughly three percent increase in sales at peak hours — because fewer customers drove away when they saw a long line. Luna: So the ROI on that thirty-minute training session must have been enormous. Lucas: They calculated that every minute of wait time reduction added about three hundred thousand dollars in annual revenue per store. So for a thousand-store chain, that eighteen-second reduction translates to roughly nine million dollars a year — from one behavior change. Luna: That's the kind of number that makes you wonder what other small gaps are hiding in plain sight in every business. Lucas: It really does. And the principle isn't limited to fast food. A hospital in Ohio applied the same idea to their emergency department triage — nurses started entering patient data into the system while walking the patient to the exam room instead of stopping at the desk to finish typing. They cut door to doctor time by over twenty percent. Luna: So the insight is: look for the moment where someone is waiting to finish one step before starting the next — and see if you can overlap them. Lucas: Exactly. It's about finding the 'idle time' that people don't even notice because it's become part of the routine. In the drive-thru case, no one had questioned the order of operations for years — it was just how you did it. The company had to actually time-stamp each keystroke to see the gap. Luna: Were there any stores where the change didn't work? Pushback from employees? Lucas: Yeah, about fifteen percent of stores saw no improvement initially. The common thread was that the order-takers were multitasking too much — they'd taken on other responsibilities like restocking napkins or answering the phone while also taking orders. The fix only works if the person at the speaker is fully dedicated to that one task during peak hours. Luna: So you need the right role design, not just the right behavior. Lucas: Right. And that's actually the second lesson: a single change can unlock big wins, but only if the surrounding system supports it. In the stores that didn't improve, the issue wasn't the typing technique — it was that the order-taker kept getting pulled away. Luna: I'm thinking about how this applies beyond service operations. Could a software team use a similar principle? Lucas: Absolutely. I've seen this called 'pairing' in software development — one person writes code while the other reviews it in real time instead of waiting for a separate code review later. The same principle of overlapping tasks to reduce handoff delays. Luna: So the core takeaway from this episode is: measure the invisible gaps, not just the visible steps. Lucas: Yeah. And that's the kind of thing you can test next week — pick one process in your business, put a stopwatch on it, and look for where people are waiting before they act. You might find your own eighteen-second gap. Luna: I like that. Small change, big leverage. Thanks, Lucas. Lucas: Thanks, Luna. See you tomorrow.