Latest / The Operations Podcast with Fexingo: Process, People, and Profit in Modern Business / How One Restaurant Chain Cut Kitchen Wait Times by 40 Percent
Transcript
- Lucas: You walk into a Sweetgreen at 12:15 on a Tuesday in midtown Manhattan. There's a line, but it moves. You order a Harvest Bowl with chicken, tap your phone to pay, step to the side. Seven minutes later your name is called. Luna: Seven minutes — that feels fast for a made-to-order salad with, what, twelve ingredients? Lucas: Right. And it wasn't always that fast. About two years ago the average ticket time across their stores was pushing twelve minutes. That's an eternity in lunch rush. So Sweetgreen did something pretty surgical: they redesigned the entire kitchen flow from the ground up. Luna: Were they just slow, or was there something structural going on? Lucas: Structural. They'd grown from a handful of stores in 2007 to over 200 by 2023. But the kitchen process was essentially the same as when they were a single shop in Georgetown. Each bowl got assembled start to finish by one person — called the 'line cook' — who had to pivot between chopping, portioning, dressing, and handing off. That's a lot of context switching. Luna: So one person owns the whole bowl. That's actually how a lot of fast-casual places operate. Chipotle does it, Sweetgreen did it. What changed? Lucas: They split the process into discrete stations. First, a 'base' station — greens, grains, warm bowl base — handled by one person. Then a 'top station' where proteins, veggies, and crunchy toppings go on. Then a 'finish station' with dressing, garnishes, and hand-off. Luna: So instead of one person doing everything, you've got three people each doing a smaller slice of the work. That sounds like a classic assembly-line split. But salads are custom — does that work? Lucas: It does, but only if the stations are sequenced correctly. Sweetgreen tested three different layouts in a prototype kitchen before settling on what they call the 'Z-flow.' The base station is at the front, top station in the middle, finish at the back. Each station has a dedicated set of ingredients within arm's reach, so the cook never has to walk more than one step to grab the next item. Luna: That's the physical layout. But what about the mental load? If I'm at the top station, I'm seeing every order come through. How do I know what goes on each bowl without reading the whole ticket? Lucas: Good question. They introduced a digital display at each station that shows only the relevant ingredients for that station. The base station sees the base and grain choice. The top station sees protein and veggies. It's filtered. The cook doesn't get overwhelmed by the full order. Luna: That's actually clever. In a traditional line, the first person has to read the entire ticket, then the second person has to recall or re-read. Here each person only sees what they need. Lucas: Exactly. And they added a 'runner' — a dedicated person who floats between stations, restocking ingredients, wiping down surfaces, and helping with the hand-off. Before, the line cooks had to stop and restock themselves, which created mini bottlenecks. Luna: So the runner role is essentially a buffer against variability. When lunch rush hits and every station is firing, the runner keeps the flow smooth without adding headcount to each station. Lucas: Right. And the results were significant. In the 20 test stores, average ticket time dropped from 12.1 minutes to 7.4 minutes — a 39 percent reduction. Order accuracy actually went up, too, because each station had fewer items to mix up. Employee turnover in those stores dropped 15 percent. Luna: Wait — turnover dropped? That's interesting. Usually when you specialize work, people find it more repetitive and burn out faster. What happened? Lucas: Sweetgreen's team found that the new system actually reduced stress. Line cooks in the old model were constantly juggling multiple orders, feeling rushed, making mistakes. In the new model, each cook has a clear, manageable task. They can get into a rhythm. And because the runner handles restocking, they're not pulled away from their station. Luna: So the work itself is simpler, but the system is smarter. That's a classic operations trade-off: you trade flexibility for efficiency, but if you design well, you can keep enough flexibility for customization. Lucas: Exactly. And Sweetgreen didn't stop there. They also changed their prep process. Before, prepped ingredients were stored in large bins that sat in a walk-in cooler. Cooks would grab a bin, bring it to the line, use it until empty, then go back for another. That created variability in how much was on hand and how often you had to restock. Luna: So they moved to a pre-portion system? Lucas: They did. Now, during the morning prep shift, ingredients are portioned into smaller containers — each container holds exactly what one station needs for, say, 20 bowls. The runner swaps empty containers for full ones. That way, stations never run out, and the cooks never have to eyeball portions. Luna: That's a pretty big change in the supply chain inside the kitchen. It shifts the complexity from the line to the prep shift. But prep is usually lower volume, earlier in the day — it's easier to standardize there. Lucas: Yes. And they standardized the container sizes and colors — green for base, red for protein, yellow for toppings. It's a visual cue system. A cook at the top station sees a red container and knows it's chicken, not steak. Luna: That's almost like the Toyota color-coding in their parts bins. Simple, but it prevents mistakes without requiring the cook to read labels under time pressure. Lucas: Exactly the same principle. And the whole rollout happened methodically. They didn't just flip a switch across 200 stores. They ran a pilot in 20 stores for six months, measuring every metric — ticket time, accuracy, labor hours, waste. Then they iterated on the layout three times before they were satisfied. Luna: That's a good reminder that operations improvements aren't one-and-done. You have to test, measure, adjust. Lucas: And the cost of the pilot was minimal — maybe fifty thousand dollars for the prototype kitchen and the digital displays. When you consider that faster ticket times mean more customers served per hour during lunch rush, the payback period was probably under three months. Luna: Look, I know this is a business show, and a lot of our listeners are running teams or companies. So if this kind of deep dive into how a real company fixed a real operational problem is useful to you — if it's moved your work forward in some small way — we want to keep doing them. And the way we keep this show ad-free is listener support. You can buy us a coffee at buy me a coffee dot com slash fexingo. That's all lowercase, one word. It helps cover the research and production time. Lucas: Yeah, we don't have sponsors, we don't run ads, and we want to keep it that way. If you've gotten value from episodes like this one, that link is how you can make sure we keep going. Now — one more thing about Sweetgreen's system that I think is worth noting. Luna: What's that? Lucas: They also changed the way they handle mobile orders. In the old system, mobile orders would pop up on the same printer as in-store orders, and the line cook had to decide which to make first. In the new system, mobile orders get routed to a separate station — a 'digital order assembly area' — with its own dedicated staff during peak hours. Luna: That makes sense. Mobile orders are typically placed ahead of time, so they need to be ready when the customer walks in. If you mix them with in-store orders, you either delay the walk-in or you miss the mobile pickup time. Lucas: Exactly. And the results again were clear: mobile order accuracy improved by 22 percent, and average wait time for a mobile pickup dropped from 5 minutes to under 2. That's a huge customer experience win. Luna: So the whole system redesign is really about separating flows — in-store vs. digital, base vs. top vs. finish — and giving each flow the right resources. Lucas: That's the core insight. Sweetgreen didn't invent any new technology. They just reorganized the work, added a runner, color-coded containers, and filtered order information. The result was a 40 percent reduction in wait time and happier employees. That's a textbook operations win. Luna: And it's replicable. Any restaurant with a made-to-order process could look at their own station layout, their own information flow, and ask: where are the handoffs causing delays? Where are the bottlenecks? Lucas: Right. Next time you're in a fast-casual place and your food comes out in under eight minutes, you might be seeing the result of a similar process redesign. Thanks for listening, and we'll see you next episode.