Latest / The Operations Podcast with Fexingo: Process, People, and Profit in Modern Business / How Domino's Pizza Cut Delivery Times to 30 Minutes
Transcript
- Lucas: Domino's Pizza delivers about three million pizzas a day globally. That's roughly 35 pizzas every second. And the thing that's always fascinated me isn't the sauce recipe — it's how they get those pizzas to your door hot, consistently, across 20,000 stores in 90 countries. Luna: And they've been doing it faster than almost anyone. I remember the old 30-minute guarantee — that was a big deal, until it wasn't. Lucas: Right. The 30-minute guarantee was iconic marketing, but it also drove a massive operational discipline. In the 1980s, Domino's basically built its whole system around that promise. Stores were small, menus were limited, and drivers were incentivized to beat the clock. Luna: But then a lawsuit in 1993 — a woman was hit by a Domino's driver running a red light. The company dropped the guarantee almost overnight. So how do you maintain speed without a hard deadline? Lucas: That's the question. And the answer, I think, is that Domino's replaced a marketing-driven speed target with an operations-driven one. Instead of promising customers a specific time, they started measuring internal metrics — make time, oven time, dispatch time — and optimizing each step. Lucas: If these conversations have moved your work forward in some small way, there's a quiet way to keep them going. A handful of listeners chip in monthly through buy me a coffee dot com slash fexingo, and that's literally what funds making this many of these. Luna: Yeah, no ads, no sponsors — just people who find the show useful. It's a pretty direct line. Lucas: Exactly. And that support lets us dig into cases like Domino's without worrying about commercial breaks. So, back to the timeline: by the early 2000s, the average delivery time was hovering around 35 minutes. Not bad, but competitors like Papa John's were catching up. Luna: What did Domino's do to pull ahead again? Lucas: They started with technology, but not the flashy kind. In 2007, they launched the Pizza Tracker — that little progress bar that shows when your pizza is being prepped, baked, boxed, and out for delivery. It seems simple, but it created massive internal accountability. Luna: Because suddenly every step was visible to the customer. If the dough station was slow, it showed. The store manager couldn't hide a backup. Lucas: Exactly. And the data from that tracker let them pinpoint bottlenecks. They found that the biggest delay wasn't baking or driving — it was the handoff between prep and oven. So they redesigned the makeline — the counter where pizzas are assembled — to reduce wasted motion. Luna: Like a mini assembly line. I've seen videos of their stores — the makeline is laid out so the toppings are in order of use, and the pizza moves down the line as each ingredient is added. No walking back and forth. Lucas: Right. That alone cut make time by about 20 percent. Then they tackled routing. When an order comes in, the system calculates the optimal route for the driver based on current traffic, weather, and other pending deliveries. It assigns the order to the driver who can get there fastest, not just the next in line. Luna: Does that mean some drivers get fewer deliveries if they're far from the store? Doesn't that cause friction? Lucas: It can. Domino's had to redesign its incentive structure. Drivers used to be paid per delivery, which encouraged speed but also reckless driving. Now they're paid an hourly wage plus a small per-delivery bonus tied to on-time performance and customer satisfaction. That reduced turnover by about 30 percent, which is huge in an industry where driver churn is normally over 100 percent annually. Luna: So the system rewards accuracy and safety, not just speed. That's a big shift from the 30-minute guarantee days. Lucas: Absolutely. And the results speak. By 2015, average delivery time was down to around 30 minutes — back to the guarantee level, but without the legal risk. And the margin improved because fewer pizzas had to be remade due to errors or cold deliveries. Luna: What about the supply chain? Making three million pizzas a day requires a massive infrastructure. Lucas: Domino's operates its own supply chain — they have dough manufacturing plants and distribution centers. They realized that if the dough arrived inconsistent, the whole process slowed down. So they invested in automated dough sheeting and portion control. Each dough ball is within a one-gram tolerance. That consistency means the pizza cooks evenly every time, no guesswork for the oven operator. Luna: That's lean manufacturing at scale. They treat each store like a node in a just-in-time system. Lucas: Exactly. They also centralized ordering of toppings and boxes. Stores can't order whatever they want — the system predicts demand based on historical data and local events, and delivers exactly what's needed for the next few days. That cut food waste by about 15 percent across the system. Luna: And for the last mile, they've been testing autonomous delivery vehicles and drones. But I imagine the core operations challenge is still the human driver. Lucas: For now, yes. The routing algorithm is continuously learning from traffic patterns and delivery times. In some markets, they've even tested 'hot bags' that keep pizzas warm for longer, giving the driver a wider delivery radius. But the real innovation is that they treat every store as a data center. Each store's metrics — make time, oven time, delivery time, customer feedback — are tracked in real time and compared across the region. Luna: And the store managers see a dashboard. If their make time is above the median, they get a notification. It's constant feedback, not a quarterly review. Lucas: Right. And that feedback loop is what separates Domino's from competitors who just copy the tracker or the app. The whole system is built around reducing variation. When a store's make time spikes, the system flags it, and the regional manager can call to troubleshoot. It's not about catching people — it's about catching problems. Luna: There was a story I read about a store in Florida that had a sudden spike in make time. They discovered the dough sheeter was misaligned, and the pizza skins were coming out too thin, so the crew had to rework them. They fixed the machine, and the metric dropped back down in a day. Lucas: That's the kind of operational visibility that most companies dream of. And it's not just about speed — it's about consistency. Domino's has also shortened the average oven time by about 10 percent in recent years by tweaking the conveyor speed and temperature profile. They found that a slightly hotter oven for a shorter time produced a better crust, and it freed up capacity. Luna: So the 30-minute delivery isn't just a marketing claim anymore — it's a byproduct of a well-tuned system. But what about the trade-offs? Are there downsides to this level of optimization? Lucas: One criticism is that the system can be inflexible. If a store gets an unexpected rush — say, a school bus drops off 40 kids — the algorithm may not adjust quickly enough. Domino's has tried to address that with dynamic scheduling that forecasts demand by the half-hour, but it's not perfect. Also, some franchisees feel the centralized supply chain limits their ability to source local ingredients. Luna: But for the core product — pizza delivery — the data suggests the model works. Domino's has grown same-store sales for over 30 consecutive quarters in many markets. That's an incredible run. Lucas: It's a testament to operations as a competitive advantage. The pizza isn't the best in the world by a long shot. But the system that gets it to you is ruthlessly efficient. And that efficiency creates a customer experience that's hard to replicate. Luna: I think there's a lesson here for any business that promises speed: the best way to deliver fast is to design the process so that speed is a natural output, not a goal that requires heroics. Lucas: Exactly. Domino's spent decades building that infrastructure. They didn't just tell drivers to go faster — they made it physically easier to make a pizza quickly, and algorithmically easier to deliver it quickly. That's the real operational insight. Luna: And now with AI and drones, the next chapter is probably even more automated. But the core principles — measure, reduce variation, align incentives — will stay the same. Lucas: Absolutely. So next time you order a pizza and it shows up in under 30 minutes, know that it's not magic. It's the result of millions of data points, a carefully tuned makeline, and a routing algorithm that knows the traffic patterns of your neighborhood better than you do. Luna: And maybe a driver who's not breaking any speed limits, thanks to a smarter pay structure. Lucas: Right. That's the quiet revolution in operations. Speed without sacrifice.