Latest / The Operations Podcast with Fexingo: Process, People, and Profit in Modern Business / How A Restaurant Chain Fixed The Table Turn Problem
Transcript
- Lucas: There is a specific kind of panic that sets in at four thirty on a Friday evening in a full-service restaurant. You have forty tables, all occupied, but the kitchen is backed up, the servers are running between three stations, and the host stand is staring at you like you owe them money. Most managers try to solve this by yelling louder or adding more bodies, which usually just creates more chaos. Luna: Right, because you end up with two people trying to clear the same table while another customer waits for water for ten minutes. It feels like you're fighting physics. Lucas: Exactly. And for years, the industry accepted that friction as the cost of doing business. But last year, a mid-sized casual dining group called Hearth & Home decided to treat the dining room not as a collection of tables, but as a pipeline. They weren't interested in serving more customers; they were obsessed with moving them through faster without making everyone feel rushed. Luna: That sounds counterintuitive. Usually, if you want more volume, you just open more seats. Why focus on speed? Lucas: Because speed drives yield. If you can increase your table turnover rate by even fifteen percent during peak hours, you effectively expand your seating capacity by fifteen percent without building a single new wall or buying a single new chair. For Hearth & Home, that meant an incremental revenue boost of nearly eighteen million dollars over twelve months, purely from existing real estate. Luna: So they didn't change the food? Or the service style? Lucas: They changed almost nothing about the product, but they radically redesigned the process. The first thing they did was audit the guest journey, minute by minute. They realized that sixty percent of the delay wasn't in the kitchen cooking time, which is largely fixed, but in the handoffs. The wait between ordering and drink delivery, the wait between eating and asking for the check, the wait for the card machine to arrive. Luna: I remember waiting for a card reader once, and it took so long I started wondering if the server had forgotten me entirely. It kills the vibe. Lucas: It kills the vibe and it caps the revenue. Hearth & Home found that the average time from finishing the meal to the guest leaving the building was fourteen minutes. Fourteen minutes where the table is technically occupied but functionally dead. They cut that to nine minutes. How did they do it without turning into a fast-food joint? Luna: I assume tech played a role. Did they put iPads on the tables? Lucas: Actually, no. That’s a common mistake. Putting devices on the table often slows down the interaction because guests fumble with them, and servers still have to walk over to confirm orders. Instead, they used handheld devices for servers, but paired it with a structural change in routing. They stopped assigning static zones. Instead, they used a dynamic zoning algorithm based on real-time seat status. Luna: Dynamic zoning. So a server isn't stuck with just the north section if the south section gets busy? Lucas: Precisely. In the old model, Server A would be drowning in Table Four while Table Two sat empty because Server B was stuck on a long lunch in the corner. The new system treats servers like units of capacity. If a table is cleared, the nearest available server gets pinged. But here is the key part: they also split the roles slightly. Not into separate bussers and servers, but into focused moments. Luna: You mean like having one person handle drinks and another handle food? Lucas: Not permanently. But they optimized the sequence. The most efficient flow they discovered was the 'drop and go' method for drinks. Servers carry trays of drinks to a quadrant, drop them off, and immediately move to the next quadrant rather than waiting at the table to pour. It sounds minor, but it eliminates the idle standing time that adds up to minutes per hour. Luna: That makes sense. You’re maximizing movement. What about the check? That’s always the bottleneck. Lucas: The check was the biggest win. They eliminated the paper check altogether for standard transactions. When the plate is cleared, the tablet pings the server’s device with the total. The server walks over, shows the screen, and the guest taps to pay or inserts a card. No printer jamming, no lost tickets, no walking back to the POS terminal. It reduced the payment phase from an average of four minutes to ninety seconds. Luna: Ninety seconds versus four minutes. That is huge. But does that feel impersonal to the guest? Lucas: That is the question, isn't it? Because if you make it too fast, people feel like cattle. Hearth & Home solved this by doubling down on the 'warmth' moments. Since they saved time on administrative tasks, they trained staff to spend those seconds on genuine connection. A better greeting, remembering a regular’s name, asking a specific question about the meal. They traded transactional time for relational time. Luna: So they automated the boring stuff to humanize the rest. I like that framework. Lucas: Exactly. And it required a shift in incentives. Previously, servers were tipped on gross sales, which encouraged them to linger or upsell aggressively. They moved to a model that rewarded table turns within a certain window, plus a bonus for high satisfaction scores. It aligned the employee’s wallet with the guest’s desire for a smooth, quick, but pleasant experience. Luna: That’s clever. Usually, incentives are misaligned. You want speed, but tips reward volume. How did they handle the backlash from older staff who liked the old way? Lucas: They didn't force it overnight. They rolled it out in one pilot location first. After three months, the servers there were earning twenty percent more on average because the higher turnover meant more shifts worth of tips, even if the individual ticket size stayed flat. Once the other locations saw the payroll data, the adoption was voluntary. It’s hard to argue with a bigger paycheck. Luna: And presumably, the guest satisfaction scores didn't tank? Lucas: They actually went up. The net promoter score improved by eight points. People hate waiting for the check more than they hate anything else in a restaurant. By removing that pain point, they removed the last negative memory of the night. It’s a great example of how operational hygiene directly impacts brand perception. Luna: It really is. If you leave happy, you come back. If you leave frustrated by the bill, you might not. Lucas: Before we dig into the second layer of this problem—the kitchen side—I want to pause for a moment. If these conversations have moved your work forward in some small way, consider supporting the show. Listener support is what keeps Fexingo independent and ad-free. You can find us at buy me a coffee dot com slash fexingo. It takes less than a minute, and it helps us keep digging into these operational details for you. Luna: Yeah, we appreciate it. Whether it’s a coffee or just sharing an episode, it keeps the lights on. Lucas: Thanks. Now, back to the kitchen. Because speeding up the front of house is useless if the back of house bottlenecks. Hearth & Home found that their kitchen lag was caused by order batching. Servers would enter orders as they came in, causing the kitchen display system to jump around chaotically. Luna: So the cooks are switching context constantly? Lucas: Exactly. One moment they’re plating pasta, the next they’re firing a burger, then checking a salad. They switched to a staged entry system. Orders entered within a thirty-second window of each other are grouped. The kitchen sees a batch: 'Two burgers, one steak, two sides.' They fire them together. It reduces setup time and keeps the line moving smoothly. Luna: That sounds like assembly line logic applied to fine dining. Does it hurt customization? Lucas: Surprisingly, no. Because the batches are small, cooks can still modify items easily. The key is that they aren't interrupted. In the old system, a cook might finish a dish, look up, see a new order pop up, and lose their rhythm. With batching, they finish a set, reset, and start the next set. It’s mental conservation. Luna: Mental conservation is such an underrated factor in operations. We talk about physical efficiency, but cognitive load matters just as much. Lucas: It does. And this ties back to the staffing model. Because the kitchen runs smoother, they needed fewer expeditors—those people who stand at the pass calling out orders. They reduced the headcount at the pass by one person per shift, but that person was reassigned to prep or cleaning. So they didn’t cut costs; they redistributed labor to where it was actually needed. Luna: That’s smart resource allocation. Instead of cutting, you just moved the asset to a higher value task. Lucas: Precisely. And it lowered turnover among kitchen staff because they weren’t working in chaos. Happy cooks stay longer. Lower turnover means lower training costs and more consistent food quality. It’s a virtuous cycle. Luna: So the ROI wasn't just revenue growth. It was also stability. Lucas: Absolutely. Stability is an asset. When you know exactly how the shift will flow, you can plan better. You can schedule breaks more accurately. You can predict inventory usage with greater precision because the waste patterns become predictable. Luna: Does this model scale? Or is it only good for mid-sized chains like Hearth & Home? Lucas: It scales very well. In fact, larger chains benefit even more because the inefficiencies are magnified. A small cafe has maybe five tables to manage. A large chain has five hundred. The compounding effect of saving two minutes per table across five hundred tables is massive. But the complexity of implementation is higher. You need robust software and strong change management. Luna: Change management is always the hardest part. Getting people to adopt new workflows when they’re tired and stressed. Lucas: Right. That’s why Hearth & Home invested heavily in simulation training before opening. They ran mock dinners with actors playing difficult guests. The staff practiced the new flows until they were muscle memory. When the real rush hit, nobody was thinking about the process. They were just executing. Luna: Muscle memory. That’s the goal. You don’t want people thinking when they should be feeling. Lucas: Exactly. Cognitive bandwidth is reserved for problem-solving, not routine tasks. Once the routine is automated through habit, the human element shines through. Luna: It’s interesting that they didn’t try to replace humans with robots. They enhanced humans. Lucas: That’s the distinction. Technology in hospitality works best as a tool, not a replacement. The robot waiter sounds cool in a pitch deck, but it doesn’t apologize sincerely when the soup is cold. It doesn’t recommend the wine pairing. It doesn’t make eye contact. The tech handled the logistics so the humans could handle the hospitality. Luna: Logistics for humans. I think that’s the future of service industries. Let the machines count the seconds, let the people count the connections. Lucas: Well said. And it leaves us with a question for anyone running a service operation: where is your friction coming from? Is it the product, or is it the process? Often, it’s the process hiding behind the product. Luna: If you remove the friction, does the product speak for itself more clearly? Lucas: It does. And that’s probably the most profitable insight of the day.