Latest / Restaurant Business with Fexingo: Food Service, Hospitality, and Independent Operators / How Your Restaurant Menu Affects Order Wait Times
Transcript
- Lucas: Let's talk about something that every operator feels but almost nobody measures: the hidden cost of a slow menu item. Luna: You mean the dish that takes forever to plate and backs up the whole line? Lucas: Exactly. Most restaurant owners think about menu profitability in terms of food cost and popularity. But there's a third variable that's just as important: cook time. And not just cook time in isolation, but how that item affects the entire kitchen's throughput during a rush. Luna: So a single slow dish can drag down the whole experience? Lucas: It can cost you real money in lost table turns and frustrated customers. I came across a case study from a 12-unit Italian chain in the Midwest. They had a baked three-cheese pasta dish that was a top seller — about 15 percent of entree orders. But it required 14 minutes in the oven, plus assembly time. During peak hours, that dish was creating a bottleneck because the oven could only fit four at a time. Luna: So they were basically running a slow-motion lottery every time someone ordered it. Lucas: Right. They eventually swapped it out for a similar but faster-cooking dish — a one-pan skillet preparation that took 6 minutes. Same food cost, same perceived value. Average ticket time dropped by 90 seconds across the whole menu. Their table turns went up by almost half a turn per night during peak periods. Luna: Ninety seconds doesn't sound huge, but over a two-hour peak, that's maybe an extra table per server per shift. Lucas: And at $60 average check, that's real revenue. The key insight here is what some operators call 'weighted average cook time.' You calculate it by multiplying each item's cook time by its order frequency, then adding them up. That gives you the average time the kitchen spends on each ticket. Luna: And if a high-frequency item has a long cook time, it skews everything. Lucas: Exactly. The Italian chain's weighted average before the change was about 8 minutes. After the swap, it dropped to 6.5. That's a 19 percent improvement in kitchen capacity without adding any equipment or staff. Luna: Let me guess — the dish that replaced it also had higher margins? Lucas: Same food cost, actually. But because it was faster, the kitchen could produce more covers per hour, which lowered the labor cost per plate. So the margin improved indirectly. That's the part most operators miss. Luna: I love that. So the real profit lever isn't just what you charge or what ingredients cost, it's how many times you can run that item through the kitchen in a night. Lucas: Exactly. I've seen this play out in other contexts too. There's a popular brunch spot in Portland that was struggling with weekend waits. They mapped every item's cook time and found that their eggs Benedict — which requires poaching eggs to order, toasting English muffins, and making hollandaise — was taking 11 minutes from fire to plate. Luna: And it was the most popular item on the menu, of course. Lucas: Of course. So instead of removing it, they redesigned the menu layout: they moved the Benedict to the bottom of the entree list and put faster items like omelets and scrambles at the top. They also added a note that said 'please allow extra time for this item.' That simple change reduced the number of Benedict orders during the peak 9 to 10 AM window by about 20 percent, because people naturally order from the top of a list. Luna: So they nudged customers toward faster items without removing the popular one. That's smart behavioral design. Lucas: And their average wait time during that hour dropped by 12 percent. Customer satisfaction scores actually went up, because the people who did order the Benedict knew to expect a wait, and everyone else got their food faster. Luna: It's like menu engineering meets operations research. I think a lot of independent operators don't have the tools to do this kind of analysis, though. They're working off gut feel. Lucas: You're right. And I want to pause here because this kind of thinking — measuring what matters — is exactly why we do this show. If these conversations have moved your work forward in some small way, a couple of dollars a month is genuinely what keeps these going. Buy me a coffee dot com slash fexingo, if you've gotten something out of them. Luna: Yeah, it really makes a difference. We don't run ads, so listener support is what keeps us independent. Lucas: Anyway, back to the data. There's actually affordable software now that can help you calculate weighted average cook time. Some POS systems can even track cook times by item if you integrate with kitchen display systems. Luna: So you can see which items are the biggest bottlenecks in real time. Lucas: Exactly. One operator I know uses a simple spreadsheet. He tracks every item's cook time, its order frequency, and its contribution margin. Then he calculates the contribution margin per minute of cook time. That's the real metric you want to optimize for. Luna: So a high-margin item that takes 10 minutes might be less valuable than a medium-margin item that takes 3 minutes. Lucas: Exactly. In that Italian chain's case, the baked pasta had a contribution margin of about $12 per order, but at 14 minutes cook time, that's about 86 cents per minute. The replacement skillet had the same $12 margin but at 6 minutes, that's $2 per minute. More than double the kitchen's earning power per unit of time. Luna: That's the kind of number that makes you rethink your menu instantly. Lucas: And it's not just about removing slow items. Sometimes you can speed up the process. A burger joint in Austin realized their signature burger took 8 minutes because the patty was cooked to order on a flat top. They switched to a par-cook method — sear the patties ahead of time, then finish them on the grill in 2 minutes. Same taste, same food cost, but the cook time dropped to 4 minutes. Luna: Did customers notice any difference? Lucas: No. And their ticket times dropped by 30 percent during lunch rush. They also reduced waste because they could predict patty demand more accurately with a par-cook system. Luna: So there are operational hacks that don't change the customer experience but dramatically improve efficiency. Lucas: Right. Another one: a pizza place in Chicago pre-bakes their crusts to 80 percent done. When an order comes in, they just add toppings and finish the bake. Shaves 5 minutes off each pizza. Luna: I've also seen restaurants use 'speed scratch' cards — pre-printed tickets for high-volume items so the kitchen doesn't have to read handwritten orders. Lucas: Small changes compound. The bottom line is: your menu is not just a list of dishes. It's a production schedule. Every item is a process that consumes kitchen capacity. If you don't measure that capacity, you're flying blind. Luna: So what's the first step for an operator who wants to start this analysis? Lucas: I'd say pick your three busiest hours. Time every item that goes through the kitchen during that window. Just use a stopwatch for a week. You'll quickly see which items are the time hogs. Then ask: can we speed this up, swap it out, or nudge customers away from it? Luna: And if you're a small independent, you might not have the data tools, but you have intuition. You probably already know which dish stresses out your line cooks. Lucas: Exactly. Trust that gut feeling, but back it up with a timer. You might be surprised by what you find. Luna: Good episode. Next time we should talk about the cost of menu changes — like, how often should you rotate items without confusing your supply chain. Lucas: That's a great topic. Let's do that.