Latest / The Operator's Manual with Fexingo: Daily Decisions, Tactical Wins, and Business Execution / How Domino's Fixed Its Pizza Quality with Ops Metrics
Transcript
- Lucas: So there's this moment in 2009 where Domino's Pizza basically admits their pizza is bad. Not just bad — focus groups called the crust 'cardboard' and the sauce 'ketchup.' And they put those quotes in a national ad. Luna: I remember that campaign. It was shocking at the time — a company trashing its own product. Lucas: Right. But the ad wasn't the real story. What happened next was an operational overhaul that most people missed because they were focused on the marketing. Domino's didn't just change the recipe. They changed how they measured every single pizza that left a store. Luna: And that's where the 'Perfect Pizza' score comes in? Lucas: Exactly. Before 2009, Domino's measured things like tickets per hour, average delivery time, food cost percentage — all the standard quick-service metrics. But nobody was measuring whether the pizza was actually good. So they created a single metric: the Perfect Pizza score. A pizza got a perfect score if it hit nine specific criteria — cheese distribution, topping coverage, crust color, cut accuracy, temperature at delivery. Each store got scored on a sample of pizzas every week. Luna: Nine criteria seems high. How do you enforce that across thousands of franchise locations? Lucas: That's the clever part. They didn't send inspectors. They built a system called the 'Pizza Checker' — a mobile app that delivery drivers used to photograph every pizza before it went out the door. The app would overlay a grid and use image recognition to check topping spread and cheese melt. It wasn't perfect, but it created real-time feedback at the store level. Suddenly, a franchisee couldn't claim ignorance — they had a daily quality score on a dashboard. Luna: So the driver becomes the quality inspector. That's a smart use of existing labor. Lucas: Exactly. And it tied directly to the customer experience. Because at the same time, Domino's launched the Pizza Tracker — that public-facing tool that shows your order status. But internally, that same data fed into the operations team. If a pizza sat in the warming rack too long, the system flagged it. If a store's Perfect Pizza score dropped below 85 percent, the regional coach got an alert. Luna: And this was all happening while they were rolling out a new recipe and new supply chain? Lucas: Yes. The recipe change got the headlines — new sauce, new crust with garlic butter, new cheese blend. But the supply chain piece is where operations people get excited. Domino's owns its own dough manufacturing and distribution. They had to reformulate the dough to handle the new recipe while still working in their existing commissary system. That meant changing the flour blend, the proofing time, the temperature controls across 17 dough plants. One plant alone produces dough for about 800 stores. Luna: So they're changing the product and the production system simultaneously. That's a high-risk move. Lucas: It is. But they had a couple things going for them. One, they'd already tested the new recipe in 12 stores for a year. Two, they had a clear north star metric — the Perfect Pizza score — so they could tell if a change was actually improving quality or not. And here's a number that sticks with me: within two years of the launch, same-store sales in the U.S. grew over 14 percent in 2010 and another 10 percent in 2011. The stock went from about $8 in 2009 to over $50 by 2012. Luna: But those results aren't just from a metric. The metric had to change behavior. Lucas: That's the key insight. The Perfect Pizza score wasn't just a dashboard number — it was tied to franchisee bonuses and store manager evaluations. If your store scored below 80 percent for three consecutive weeks, you got a visit from a quality coach. Not a punitive visit — a coaching visit. The company invested in training teams on how to use the scoring tool to identify root causes. Like, if your topping coverage was poor, maybe the portioning scale was off, or the crew wasn't trained on the correct hand-stretching technique. Luna: So it turned the metric into a diagnostic, not just a report card. Lucas: Exactly. And they built a feedback loop that fed back into product development. If stores across the country were consistently failing on cheese melt, the R&D team knew they needed to adjust the cheese blend or the oven temperature. That's how you operationalize continuous improvement — not through slogans, but through data that tells you where to look. Luna: I want to talk about the customer side of this. The Pizza Tracker — most people see it as a convenience feature, but it's also an ops tool, right? Lucas: Absolutely. Domino's was early in using customer-facing technology to drive operational accountability. When a customer watches their order move from 'prep' to 'bake' to 'quality check' to 'delivery,' they're implicitly being trained on Domino's process. And if a pizza sits in 'quality check' for too long, the customer sees it. That creates pressure on the store to move pizzas through — but in a way that's transparent. It also gave Domino's a massive dataset on real-time order flow. They could predict peak periods and staff accordingly. Luna: And they layered that with the delivery tracking. By 2014, Domino's had a gps based delivery tracker that let customers see their driver's location. That's not just convenience — it reduces 'where's my pizza' calls, which frees up in-store staff. Lucas: Right. Every call that doesn't happen is labor saved. And those labor savings get reinvested into quality. The whole system is designed to close loops: customer feedback goes to the store, store performance goes to the coach, coach feedback goes to supply chain and R&D. It's a closed-loop operations model. Luna: And it's worth noting that Domino's isn't a tech company — they're a pizza company that uses technology to execute operations better. That's a distinction that matters. Lucas: It absolutely matters. They didn't try to become a software company. They built tools that solved specific operational problems: how do we know the pizza is good before it leaves the store? How do we reduce phone calls? How do we forecast demand? And they made those tools simple enough that a 17-year-old crew member could use them on a Friday night rush. Luna: Speaking of Friday night rush — what about the delivery drivers themselves? The Pizza Checker app adds time to their pre-delivery process. Did that ever create pushback? Lucas: There was pushback early on. Drivers complained that snapping a photo and waiting for the app to verify quality added 10 to 15 seconds per order. But Domino's framed it as part of the job — you're not just delivering pizza, you're guaranteeing quality. And they tied it to the tip. If the pizza looks good when it arrives, customers tip better. Over time, drivers saw that the system actually increased their earnings. So adoption improved. Luna: So the operational fix had to align with individual incentives at every level — franchisee, manager, driver. That's hard to get right. Lucas: It's the hardest part. You can build the best dashboard in the world, but if people don't have a reason to use it, it's decoration. Domino's succeeded because they made the metric matter at every level. Franchisees care about profit — quality scores correlated with higher sales and lower complaint costs. Managers care about their bonus — quality scores were a direct input. Drivers care about tips — better quality meant better tips. Luna: And the company itself cared about consistency at scale. That's the part that makes this a case study worth studying. Lucas: Honestly, if today's episode was worth a coffee to you, that's the link — buy me a coffee dot com slash fexingo. No pressure, but listener support is what keeps this show independent and ad-free. Luna: Yeah, it's a small way to say this kind of deep-dive content matters. We appreciate everyone who chips in. Lucas: Back to Domino's — one more piece I want to highlight. In 2015, Domino's launched 'Domino's DXP' — a custom delivery vehicle with a warming oven built into the back. It was a bit gimmicky, but it reflected their obsession with the last mile of quality. They understood that a perfect pizza that sits in a cold car for 15 minutes isn't perfect anymore. So they engineered the delivery vehicle itself. Luna: That's the kind of thinking that separates the good operators from the great ones. They looked at the entire chain from dough to doorstep. Lucas: Exactly. And the results speak for themselves. By 2019, Domino's had become the largest pizza company in the world by sales, surpassing Pizza Hut. And they did it not by being cheaper or flashier — but by being operationally relentless about a single question: is the pizza good when it arrives? Luna: So what's the takeaway for a business that's not in pizza? What can a B2B SaaS company or a retailer learn from Domino's? Lucas: I'd say two things. First, pick one outcome metric that actually captures what your customer values — not what's easy to measure. Domino's could have measured delivery speed or cost per pizza. They chose quality. Second, build feedback loops that connect that metric to daily behavior at every level. The metric alone changes nothing. The system around the metric changes everything. Luna: And be willing to admit your product isn't perfect — then fix it. That takes a certain kind of operational humility. Lucas: It does. And that's probably the hardest operational decision of all: saying 'our current process isn't good enough' and then designing a system to prove it every single day.