Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How One Pizza Chain Cut Delivery Times 12 Percent With One Kitchen Change
Transcript
- Lucas: Last week I was talking to the owner of a small pizza chain in Ohio. He told me their biggest complaint wasn't taste—it was delivery time. They had a target of 30 minutes from order to door, but they were averaging 38. And the bottleneck wasn't the oven or the driver. It was the six feet between the packaging station and the pickup window. Luna: Six feet? That's barely a step. Lucas: Exactly. But every driver had to walk to that station, pick up the order, walk back. Multiply that by 150 deliveries a night, and you're losing about 20 minutes of cumulative time during peak hours. So they moved the packaging station six feet closer to the window. Cost: about $300 in labor to rearrange tables. Luna: That's the kind of simple fix that makes you wonder what other small changes are hiding in plain sight. Lucas: It really does. And it's exactly the kind of thing we dig into on this show. If these conversations have helped you spot a similar tweak in your own work, you can support us at buy me a coffee dot com slash fexingo. Keeps the podcast ad-free. Luna: Yeah, we appreciate it. Now, the real question is—did the move actually work? Lucas: It did. Their average delivery time dropped from 38 minutes to 33.4 — a 12 percent improvement. And customer survey scores went up eight points. Luna: Eight points on what scale? Lucas: They use a one-to-five scale. So from a 3.9 to a 4.2. Which doesn't sound huge, but for a chain with 15 stores and thin margins, that's material. They also saw a small uptick in repeat orders from customers who had previously complained about late deliveries. Luna: So the owner just... decided to move the table one day? Lucas: Pretty much. He said he'd been frustrated for months watching drivers hover. Then one slow Tuesday, he and the store manager physically slid the table over. It took about 15 minutes. They tested it for a week, and the numbers spoke for themselves. Luna: I love that. No consultants, no software. Just a tape measure and some elbow grease. Lucas: Right. And the key insight is that they didn't try to speed up the kitchen or add more drivers. They removed a tiny bit of friction that was compounding. That's the spirit of lean operations—find the place where work-in-progress piles up, and ask why. Luna: Was there any downside? Like, did the packaging station being closer to the window cause crowding or mix-ups? Lucas: Great question. The owner said the first few shifts felt a little cramped, so they adjusted the angle of the table slightly. But within two days, the crew adapted. And because the packaging area is now adjacent to the dispatch window, the handoff is smoother—fewer shouted orders. Luna: So the fix wasn't just a physical move; it also changed the communication flow. Lucas: Exactly. The packaging person now hears the driver call out the order number without having to turn around. That shaved another second or two per order. Not huge alone, but it adds up. Luna: I'm thinking about other businesses where a similar layout tweak could apply. Like a fast-casual restaurant where the pick-up counter is on the opposite side of the kitchen from where orders are bagged. Lucas: Right. Or a retail warehouse where the packing station is far from the shipping dock. The principle is the same: any time a person or item has to travel a distance that doesn't add value, you have a candidate for a move. Luna: What about the cost-benefit? They spent $300 in labor, but what was the return? Lucas: They calculated that the 4.6-minute reduction in average delivery time meant drivers could squeeze in an extra delivery per hour during peak. At an average ticket of $22, and with about 20 peak hours per week across all stores, that's roughly $1,000 per week in incremental revenue. So the $300 paid for itself within a day. Luna: Wow. And that's not even counting the customer retention gains. Lucas: Exactly. The owner told me that before the change, they were losing about 5 percent of first-time delivery customers to competitors—mostly because of late arrivals. After the change, that number dropped to under 2 percent. Hard to quantify exactly, but definitely real. Luna: So this is a classic example of what operations people call 'takt time' alignment. The packaging station's cycle time was slower than the demand rate, causing a queue. But the real problem was the handoff distance, not the packaging speed. Lucas: Bingo. And that's the trap: when you see a pileup, you often assume you need more capacity—faster equipment, more people. But sometimes the bottleneck is just a routing issue. In this case, the packaging station itself could handle the volume; the drivers just couldn't get to the orders fast enough. Luna: What about other stores in the chain? Did they roll out the change? Lucas: They did. Within a month, all 15 stores had moved their packaging stations. Not all saw a 12 percent improvement—some stores had slightly different layouts. But the average gain across the chain was about 8 percent. And it cost nothing beyond the initial test. They just issued a memo with a diagram. Luna: That's the beauty of a standardized process: once you find a winning tweak, you can clone it across locations. Lucas: Exactly. And the owner told me they're now doing a monthly 'walk the line' session where managers look for exactly this kind of friction. They've since moved the drink cooler closer to the drive-through window, and they rearranged the topping station to reduce steps for the pizza makers. Luna: So the culture of continuous improvement took hold. One small change led to a mindset shift. Lucas: Exactly. And the best part is, none of those subsequent changes cost more than $200. They're all simple, low-risk moves that add up over time. Luna: I think the takeaway here is that you don't need a six-sigma black belt to improve operations. You just need to look for the places where people or things are moving unnecessarily. Lucas: Right. And measure what happens when you remove that movement. In this case, the owner had the data—delivery times, customer surveys—to confirm the impact. Without that, he might have dismissed the idea as too small to matter. Luna: What about companies that don't have that data? How can they find similar opportunities? Lucas: They can start by spending 15 minutes watching a process. Just stand in one spot and track the flow. Note where batches form, where people wait, where someone has to walk to get something. Often the fix becomes obvious. In this case, the owner literally saw drivers standing around after the packaging station moved—he knew the wait was gone. Luna: So observation, measurement, then a low-cost experiment. That's the playbook. Lucas: Exactly. And the experiment doesn't need to be a big bet. Move a table, change a sign, adjust a schedule. See what happens. If it works, keep it. If not, change it back. Luna: I love that this story came from a small chain. It's easy to think operational excellence is only for huge corporations with dedicated teams. Lucas: Absolutely. The owner said he learned this from watching how his mother ran her kitchen—everything within arm's reach. He just applied that logic to his business. Sometimes the smartest operations move is to look at how your grandmother organized her kitchen. Luna: That's a great image to end on. Next time you're waiting for a delivery, just think: maybe the fix was six feet away. Lucas: And maybe your own business has a six-foot fix hiding in plain sight.