Latest / The Operations Podcast with Fexingo: Process, People, and Profit in Modern Business / How a Coffee Chain Cut Drive-Thru Wait Times by 45 Percent
Transcript
- Lucas: So there's a regional coffee chain in the Pacific Northwest — I won't name them because they're privately held and they like it that way — but they pulled off something that most quick-service operators would tell you is nearly impossible. They cut their average drive-thru wait time by 45 percent over twelve months, and they did it without adding a single new lane or a second window. Luna: That's a big deal. I've read that the drive-thru is like seventy percent of sales for a lot of coffee shops now. Cutting wait time by that much must have moved the needle on revenue. Lucas: It did. Their same-store sales were up about eight percent in that period, and they attribute a solid chunk of that to the faster drive-thru. But the interesting part isn't the outcome, it's how they got there. They didn't throw technology at the problem. They actually took a step back and mapped the entire drive-thru experience, from the moment a car enters the queue to the moment it pulls away. Luna: So a classic time and motion study, but for coffee. Lucas: Exactly. And what they found was that the biggest bottleneck wasn't the barista making the drink. It was the order-taking process. The average customer spent thirty-eight seconds at the speaker box, and that was just too long. The team realized that a lot of that time was eaten up by the conversation itself — customers asking questions, baristas suggesting add-ons, the back and forth about sizes and milk alternatives. So they redesigned the menu board to be simpler, with fewer options and clearer categories, and they trained the order-takers to use a more scripted approach that cut down on the chatter. Luna: But wouldn't that hurt the customer experience? Some people like the personal touch. Lucas: That's exactly what they worried about. So they tested it in a handful of stores first. The satisfaction scores didn't drop, and in fact they went up slightly, because people cared more about speed than they did about the small talk. The script wasn't robotic, either. It was more like a set of guardrails — the order-taker was trained to confirm the key details early, like size and drink type, and to hold off on the upselling until after the core order was locked in. That alone cut about twelve seconds off the average order time. Luna: Twelve seconds is huge when you're talking about a whole queue of cars. But that's just the order-taking side. What about the actual making of the drink? Lucas: Right. The second big change was on the production side. They introduced a kitchen display system — it's a screen that shows the order in real time, prioritized by how soon the car is expected at the window. Previously, the baristas were working from printed tickets, and they'd just grab the next one in the pile. That sounds fine, but it meant that a single large order could block up the whole workflow. The new system lets them see the queue at a glance and start working on the drinks that are due first. Luna: So it's like a triage system for espresso. Lucas: Exactly. And they paired that with a slight reordering of the physical workspace — moving the milk steamer closer to the espresso machine, rearranging the syrup bottles, just small tweaks that reduced the number of steps a barista had to take per drink. They measured that the average time from order to handoff dropped from ninety seconds to about fifty-five. Luna: That's a massive improvement. But I'm guessing the hardest part wasn't the layout or the screens. It was getting the staff to actually change how they work. Lucas: You've hit it. The initial pushback was real. Baristas felt like they were being turned into robots, and the new script felt unnatural at first. So the chain did two things. One, they involved the baristas in the redesign from the beginning — they ran focus groups and pilot tests, and they let the staff suggest their own tweaks to the script. Two, they rolled it out slowly, one store at a time, with a lot of coaching and feedback. They also changed the incentive structure — instead of just tracking drive-thru times, they started tracking a composite score that included customer satisfaction and accuracy, so nobody felt like they had to sacrifice quality for speed. Luna: That's smart. If you only measure speed, people will game it and rush orders, and then you get mistakes and angry customers. The composite score keeps everyone honest. Lucas: Right. And the third change was on the staffing model. They looked at the peak hours — typically seven to nine in the morning and four to six in the afternoon — and they shifted some of their part-time staff to overlap those peaks, so they had an extra person on the drive-thru during the rush. They also cross-trained everyone so that any team member could jump between taking orders, making drinks, and handing out at the window. That flexibility meant they could adapt to unexpected surges without having to overstaff the whole day. Luna: So it's not just about hiring more people, it's about deploying them better. That's a classic operations lesson. Lucas: Exactly. And the results speak for themselves. Average wait time went from four minutes and twenty seconds to two minutes and twenty-five seconds. The forty-fifth percentile of orders — the ones that used to take five minutes or more — came down to under three minutes. And they didn't see any increase in order accuracy issues or customer complaints. In fact, their Net Promoter Score went up by eleven points. Luna: Those are impressive numbers. But I'm curious — did the simplification of the menu actually hurt sales? I mean, if you cut options, you might lose people who want something specific. Lucas: That was the risk. They trimmed about twenty percent of their menu items, mostly the slow-moving specialty drinks that only a few people ordered. What they found was that the customers who did order those items just switched to something else, and the overall ticket size stayed flat. But the average transaction time went down, which meant they could serve more customers per hour. So the revenue per hour actually went up. Luna: It's a classic trade-off — variety versus speed. And in this case, speed won, because that's what the majority of customers cared about. Lucas: Yeah. And they learned that lesson in a pretty direct way. In one of the test stores, they originally kept the full menu but tried a bunch of other tweaks, and the wait times only dropped by about fifteen percent. It was only when they simplified the menu that the other changes really clicked into place. The two worked together. Luna: So it's not just one silver bullet. It's a combination of factors that reinforce each other. Lucas: Right. And I think that's the takeaway for any business that's trying to improve a process — you can't just pick one thing and expect it to fix everything. You have to look at the whole system. The order-taking, the production, the staffing, the menu — they're all connected. Change one and you might get a small improvement. Change them all together, and you can get a step-change. Luna: That reminds me of something I read about Toyota's lean manufacturing. They don't just optimize one workstation; they look at the entire value stream. It's the same principle. Lucas: Exactly. And it's not just for manufacturing. This coffee chain is a perfect example of applying lean thinking to a service business. They didn't have to invest in fancy new equipment or a bigger building. They just looked at the flow of work and removed the friction. Luna: And the fact that they involved the employees from the start — that's a lesson in change management too. People are more likely to embrace a new process if they feel like they had a hand in creating it. Lucas: Absolutely. The baristas didn't just get told what to do. They helped design it. And the company made it clear that the goal wasn't to turn them into machines; it was to make their jobs easier and less stressful during the rush. When they saw that the new system actually made the flow better, the resistance faded pretty quickly. Luna: It's a nice example of how operational efficiency and employee satisfaction aren't mutually exclusive. In fact, they can feed each other. Lucas: Right. And the last thing I want to highlight is the measurement piece. They didn't just set a goal and hope for the best. They tracked everything — average wait time, order accuracy, customer satisfaction, employee turnover. They reviewed the data weekly, and they made adjustments based on what they saw. That continuous improvement mindset is what kept the momentum going even after the initial rollout. Luna: So it's not a one-time project. It's an ongoing practice. Lucas: Exactly. And I think that's a big reason why they were able to sustain the gains more than a year later. The drive-thru wait times have stayed low, and the team is still finding small ways to shave off a second or two here and there. Luna: It's funny you mention the sustained gains. That's actually a big reason why we love doing this show — it's about real, practical lessons that people can take and apply in their own work. And we're able to keep doing this because of our listeners. We don't run ads on Fexingo, and we'd like to keep it that way. If these conversations have moved your work forward in some small way, and you want to support that, the link is buy me a coffee dot com slash fexingo. It's a small gesture, but it genuinely helps us keep the lights on. Lucas: Yeah, and we really appreciate it. But look, we've got more to dig into. So back to the coffee chain. One thing I didn't mention is that they also changed their drive-thru layout slightly — not the lane itself, but the placement of the menu board and the speaker box. They moved the menu board about ten feet further back, so that customers had more time to look at it before they got to the speaker. That actually reduced the number of 'uh, hold on' moments at the order box. Luna: Oh, that's clever. It's like giving the customer a head start on decision-making. I bet that alone saved a couple of seconds per order. Lucas: It did. They measured that the average time at the speaker box dropped by another four seconds after that layout tweak. And it wasn't expensive to implement — just moving a sign and re-striping a bit of pavement. Luna: It's a good reminder that sometimes the simplest changes can have a big impact. You don't always need a high-tech solution. Lucas: Right. And I think that's the real story here. They took a systematic approach, but they didn't over-engineer it. They used data, but they also used common sense. And they had the discipline to see it through. Luna: So what would you say is the one thing a listener could take away from this episode and apply to their own business, even if they're not in coffee or fast food? Lucas: I'd say: map your customer's journey, find the biggest bottleneck, and then tackle it with a cross-functional team. Don't just guess — measure. And don't be afraid to simplify your offering if that's what's slowing you down. The coffee chain cut their menu and it didn't hurt. Sometimes less really is more. Luna: That's a great note to end on. Thanks for listening, everyone. Lucas: Yeah, take care.