Todd Duplechan has run Lenoir in Austin for 14 years. It has earned a reputation, kept a loyal following, and survived COVID. By any reasonable measure, it's a success.
So when someone recently asked him what his favorite restaurant in Austin was, the answer surprised even him.
"If I was going to rank restaurants, Lenoir probably wouldn't be in my top 30 restaurants in Austin, Texas. It doesn't calculate that way. It's not my favorite restaurant."
That's a jarring thing to admit about a place you've built with your own hands, with your spouse, over a decade and a half. But Todd wasn't being self-deprecating. He was diagnosing something real: a restaurant without documented roles, clear kitchen SOPs, or structured staff training becomes hard to work in for everyone, including the owner.
Because one month into running Bonnie's, the bar he just opened next door on the same block, he gave a completely different answer: "This might be my favorite bar. I really dig it here."
Same chef. Same block. Completely different experience of running each place. The difference wasn't the food or the concept. It was the presence or absence of clear roles, documented kitchen procedures, and a training system people could actually follow.
The Restaurant You Build vs. The One You'd Actually Go To
When Todd opened Bonnie's, he built it for himself. Not for critics, not for a mission statement. He asked what kind of bar he personally wanted to spend time in, and built that: tight roles, no elaborate pre-opening systems theater, and a focus on getting into operations as fast as possible.
Lenoir was built the other way: mission-first, concept-driven, every decision filtered through sustainability and food security.
"The mission of Lenoir is about farm to table. You start with the farmer and create as many new farmers in central Texas as we can. It's about sustainability. It's about food security. And that's been our focus. And honestly, whenever I think about Lenoir, I just see untapped potential every day. It could be so much more, which is partially why we do it, but also partially, it's a solitary confinement sentence."
Those values matter. But they don't make a kitchen easier to work in. Role clarity does. Documented kitchen procedures do. A restaurant operations manual that tells each person exactly what they own (and what they don't) does.
That gap between what you build and what you'd actually want to run is almost always a systems and documentation gap in disguise.
Listen to the full episode: Is Your Restaurant Your Favorite Place to Be? with Todd Duplechan
Why Restaurants Become Hard to Work In: The Role Drift Problem
Here's what Todd discovered while hiring a new service manager at Lenoir: the restaurant had become exhausting to work in because no one had ever clearly defined where one job ended and the next began. There were no written SOPs, no defined role scope, no culinary documentation that held the line.
The new manager said he didn't want to work 50-hour weeks. Todd's first instinct was to pass. Then he asked a harder question: What if that's not a problem with this guy? What if that's a problem with how we've structured every role in this building?
"I sat with it and I thought about what our problems are and our problems are that this place is too hard to work in. What if we limit what he does and say, this is what you do — you're going to be in charge of service and making sure that service runs great. Training is good. The schedule is right. You're not going to do the wine list stuff. You're not going to worry about planning parties. But anything that's wrong with service, I'm coming to you."
So instead of handing the new manager everything the previous one did, Todd gave him one thing: own service. Not the wine list. Not event planning. Not the 40 other things that had slowly accumulated in the role because someone had to do them and the job description had never been enforced.
Then he applied that same logic to every position: dishwasher, line cook, lead line cook, sous chef. What does mastery of this specific job actually look like? And what are we loading onto people that has nothing to do with the job they were hired for?
"I have for a long time been trying to make people into what their next job is going to be. And what I realized is that's unfair because I'm pushing stuff on them constantly. Take on more, take on more, instead of just being like: master this thing."
This is role drift. It's how restaurants quietly break their own people: not through one dramatic moment, but through the slow accumulation of undefined work that spills across every position until no one is great at anything because everyone is stretched across everything.
Without documented kitchen SOPs, role drift is almost impossible to stop.
Good restaurant staff training starts by defining the job before trying to train for it. Most operators get this backwards. They build elaborate onboarding programs and then wonder why nothing sticks. It doesn't stick because the role underneath it keeps shifting.
The Industry Data Behind Todd's Instinct
This isn't just one restaurant's problem. The data validates it at industry scale.
According to the 2026 State of Restaurants Report, industry-wide employee turnover continues to exceed 75 percent, at a replacement cost of roughly $5,864 per employee. For a mid-size restaurant group, unchecked turnover can quietly consume more than $100,000 per year.
A Restaurant Dive survey found that over 30 percent of operators cited better restaurant training programs as a top retention driver.
"When employees see a clear trajectory — how they grow, how their pay improves, and how they contribute to the guest experience — they stay."
Modern Restaurant Management's 2026 Survival Playbook identified "training burdens when staff turnover is high and experience levels are lower" as one of the most material hidden operational costs operators now track, right alongside software bloat, waste, and missed orders.
A joint study from early 2026 found that restaurant locations with low-turnover, well-trained teams consistently earn higher guest review scores, higher NPS, and stronger comp sales. The researchers put it plainly: "Retention isn't just an HR issue. It's a measurable driver of financial and brand performance."
The restaurant that's hard to work in is also, reliably, the restaurant that's expensive to run.
Why This Gets Worse at Multiple Locations
Role drift plays out painfully in a single restaurant. At multiple locations, it compounds into a full training and consistency crisis.
When roles aren't defined and kitchen SOPs don't exist in written form, your recipe documentation and staff onboarding suffer the same fragmentation.
Someone is nominally "responsible" for keeping recipes updated, but when they leave, the knowledge walks out with them. Someone is supposed to train new line cooks, but with no standard operating procedures for the kitchen, every cook gets a different version of the job depending on who happened to be standing there on their first shift.
Todd described exactly this dynamic in how Lenoir's small size makes the problem even more acute:
"You come up through the industry in New York and you are pushing and everything's difficult anyway, and then you bring that here and you're like, I expect the same thing from you guys: come to work every day with the fire and the drive and the willingness to overcome obstacles at every moment. And at a certain point you're like, it's just not realistic."
FSR Magazine has reported that more than half of restaurant employees leave within their first year when they aren't receiving the training they need or want. Industry experts told Modern Restaurant Management heading into 2026 that restaurants are increasingly "relying on newer, less-experienced team members at the same time guests are paying more and expecting more."
That squeeze of greener staff against higher guest expectations makes restaurant SOPs and structured culinary onboarding not a nice-to-have, but an economic survival requirement.
As one multi-brand operator wrote in Modern Restaurant Management: "Every location runs a bit differently, but hiring practices, onboarding steps and compliance frameworks MUST be standardized."
Understanding what effective kitchen management actually looks like at scale means accepting that your systems, not your people, are either the problem or the solution.
The groups running tight operations across 10, 20, or 50 locations aren't the ones with the most talented teams. They're the ones who documented their kitchen procedures, built a recipe training system, and held the line on what each role actually owns.
Defined Roles Require Documented Kitchen Standards
You can't define a role in a conversation and expect it to hold. It has to be written down.
The service manager needs a documented list of what he owns. The line cook needs a recipe SOP that doesn't change based on who printed it last. The sous chef needs culinary training materials that cover the same steps regardless of which location they're working.
This is precisely the gap that recipe training software and kitchen knowledge management tools like meez are built to close. When recipes live in binders, shared Google Docs, or someone's memory, role clarity is impossible because the foundational materials that define the job aren't consistent.
As meez's guide on recipe training makes clear: this isn't a people problem. It's a culinary documentation and knowledge management problem.
"The biggest opportunity [in restaurant technology] lies in tools that can improve frontline performance, giving managers clearer visibility into where each team member excels, where they struggle, and how their actions impact revenue and guest experience."
Tortazo, Chef Rick Bayless's fast-casual concept across four locations, centralized their recipes and training documentation in meez and saved 15-20 minutes per staff member per day. That’s over 30 hours per month.
Not because the food changed, but because everyone finally had the same clear source of truth to work from. Fewer recipe errors. Fewer miscommunications. Less time managing exceptions and more time executing consistently.
That's what role mastery actually requires: defined responsibilities and the documented kitchen procedures that make those responsibilities executable. One without the other doesn't hold.
The Check-In System That Keeps Standards from Drifting
One more thing Todd mentioned that operators often overlook: he and his business partner Jess have a standing weekly meeting. It covers finances, operations, and crucially, how they're each actually doing.
"Without that kind of weekly check-in or constant check-ins — what are the things that are eating at you, how can we deal with those things — I don't think it would work. We've been beat down enough that if your partner says, 'I think you need to do better at this,' you hear it and you go: okay. I don't get defensive. It's like, I'm going to think about it and I'm going to get back with you."
That meeting is their restaurant operations playbook in practice. The equivalent for your kitchen team is a recurring rhythm that surfaces what isn't working before it becomes a crisis: weekly one-on-ones, regular recipe audits, scheduled training check-ins.
The operators who build those rhythms into the structure create the feedback loops that keep role clarity from drifting back into chaos.
A restaurant operations manual or knowledge base only works if someone is responsible for keeping it current. Todd and Jess do it weekly. The best multi-unit groups do it systematically, with version-controlled recipes and training materials that update automatically when the menu changes, so the check-in reveals operational gaps rather than documentation ones.
Ask the Question: Is My Restaurant My Favorite Place to Be?
Todd's question, is my restaurant my favorite place to be?, is a useful diagnostic for any operator. But the operational follow-up is the real one:
- Do my people know exactly what their jobs are?
- Have they had a real chance to master those jobs?
- Are standards they're supposed to hit written down somewhere accessible?
- Do they exist only as unspoken expectations in your head?
"Even small tweaks, like standardizing checklists, cleaning up your onboarding process, automating repetitive tasks, can make a huge difference. The goal isn't perfection. It's freeing your team to focus on leading and serving people, not fighting systems."
Most restaurants that feel hard to work in aren't suffering from bad food or the wrong concept. They're suffering from role drift: the slow, invisible accumulation of undefined work that makes everyone feel stretched and nothing feel owned.
Fixing it doesn't require a rebrand or a new hire. It requires the discipline to document what the job is, build kitchen SOPs that hold that definition in place, and give people the recipe training tools to actually execute it.
That's how you build a restaurant you'd want to go to every day, whether you own it or work in it.
Want to see how meez helps culinary teams build recipe SOPs, standardize kitchen training, and roll out consistently across locations? See how meez works for training leaders.
FAQ
What is a restaurant SOP?
A restaurant SOP (standard operating procedure) is a written document that defines exactly how a specific task, role, or process should be executed in your kitchen or front of house. Good restaurant SOPs cover recipe procedures, prep checklists, opening and closing tasks, and role-specific responsibilities. They eliminate ambiguity, reduce training time, and make it possible to hold people accountable to a consistent standard.
Why do restaurant staff training programs fail?
Most restaurant training programs fail because they front-load information without defining role ownership first. Employees are trained on everything at once, reach a shallow level of memorization, and never develop real mastery of their specific job. FSR Magazine reports that more than half of restaurant employees leave within their first year when they aren't receiving the training they need, which usually means training that's too broad, too inconsistent, or not tied to a documented standard.
How do you build restaurant SOPs that actually get used?
Effective restaurant SOPs are short, specific, and tied directly to a role. Instead of a 40-page operations manual, build modular SOP documents for each position: a line cook SOP, a prep cook SOP, a service manager SOP, with clear ownership, defined tasks, and links to the relevant recipes or procedures. Treat them as living documents: update them when the menu changes, when a new location opens, or when a recurring training gap surfaces. The best restaurant knowledge bases are never finished.
What's the difference between recipe training and kitchen SOPs?
Recipe training focuses on teaching staff how to execute specific dishes consistently: correct technique, correct yield, correct plating. Kitchen SOPs are broader; they define how a role operates across the full shift, from prep through close. Both are required for consistent execution. Recipe training without SOPs produces inconsistent behavior around the recipe. SOPs without recipe training produce cooks who follow the process but get the food wrong. See meez's kitchen training software for how leading operators connect both.
How does recipe documentation software help with restaurant training?
Recipe documentation and training software like meez centralizes all recipe SOPs in one place, makes them accessible on any device on the line, and ensures every cook at every location is working from the same version-controlled standard. Instead of recipes living in binders, Google Docs, or someone's memory, they become a live knowledge base that updates instantly across all locations. Tortazo saved 15–20 minutes per staff member per day simply by moving from scattered documentation to a single source of truth.
How do you standardize training across multiple restaurant locations?
Multi-location restaurant training consistency requires three things: a centralized recipe and SOP library that's identical across all locations, a defined onboarding sequence for each role, and a regular audit or check-in rhythm to catch drift before it compounds. The groups that execute consistently at 10 or 50 locations document their kitchen procedures and enforce them as a non-negotiable standard across every location. For a deeper look, see how meez supports multi-unit restaurant operations.
What does role clarity have to do with restaurant turnover?
A lot. The 2026 State of Restaurants Report found turnover rates exceeding 75 percent industrywide, at a replacement cost of roughly $5,864 per employee. A consistent driver of early attrition is unclear expectations: employees who don't know exactly what their job is, who don't have documented standards to follow, and who are constantly being handed responsibilities outside their role scope. Defining roles tightly, documenting them clearly, and giving people the space to actually master one thing before expanding to the next is one of the highest-ROI retention investments an operator can make.
