Recipe Standardization: Why Consistency Isn't a Secret Recipe

Every Friday for two years, Jenn Saesue and Chat Suansilphong showed up to the same meeting.

They weren't refining a flagship restaurant or preparing for a high-profile opening. They were trying to solve a far more specific problem: how to make an allergen-free cake that tasted so good no one would guess it was allergen-free.

So they kept testing.

Alongside acclaimed baker and food scientist Melissa Weller, the founders of Fish Cheeks and Bangkok Supper Club baked, tasted, adjusted, and started over. Week after week, they chipped away at the variables until they had something they trusted, not just because it tasted right, but because it could be reproduced consistently.

That story says as much about how they think as restaurateurs as it does about how they bake. On the meez Podcast, that mindset surfaces again and again.

Many restaurant founders believe the value of a dish lives in the recipe itself. Protect the formula. Guard the spice blend. Keep the ratios in your head.

Saesue and Suansilphong have reached almost the opposite conclusion.

Recipes aren't what make restaurants scalable. Systems are.

The real challenge isn't creating a great dish. It's creating one that tastes the same when the founders aren't in the kitchen, when the staff is stretched thin, and when an ordinary Tuesday looks nothing like a perfect day.

That requires much more than a recipe. It requires a standard everyone can execute.

“Not everyone's gonna come like into the store, perform at a hundred percent level every single day.”

That simple observation becomes the foundation for everything that follows. Great restaurant systems don't assume flawless execution. They make consistency possible even when people aren't operating at their best.

The Recipe Was Never the Secret

For all the attention restaurants give to protecting recipes, Suansilphong isn't convinced they're worth protecting.

Recipes leak. Employees move on. Line cooks talk. Eventually, if someone wants the formula badly enough, they'll find it.

That's never been the real competitive advantage.

"Everyone has a recipe. If you let people make it, the recipe will leak. I think our secret is to keep sourcing the best product."

Execution Is the Competitive Advantage

That perspective shifts the conversation away from secrecy and toward execution.

Podcast host Josh Sharkey, a chef himself, echoed the same idea: two cooks can work from the exact same recipe and produce completely different results. If the ingredients aren't equally fresh, if produce has deteriorated, or if someone cuts corners during prep, the recipe hasn't changed. Everything around it has.

That's why recipe standardization isn't about hiding information.

It's about documenting the details that actually influence the final dish:

• Ingredient specifications
• Sourcing decisions
• Preparation techniques
• Weights instead of rough measurements
• Subtle notes that rarely survive on a printed recipe card

The recipe is only one part of the system. The system is what makes the recipe repeatable.

Consistency Isn't Built Around Your Best Employee

One of Saesue's most practical insights has nothing to do with recipes. It has to do with expectations.

She doesn't design her kitchens around the assumption that everyone will perform perfectly every shift. She designs them around reality. People get tired. New employees are still learning, and busy services create mistakes.

If maintaining quality depends on one exceptional cook having a perfect night, the system is already fragile.

Build for the Average Shift, Not the Perfect One

That's why she's comfortable adopting equipment or processes that remove unnecessary variability. When she looked at buying a dough sheeter in Canada, the goal wasn't to replace craftsmanship. It was to reduce physical strain and make excellent execution easier to repeat.

Consistency shouldn't depend on heroics. It should depend on systems.

Standardization Makes Training More Resilient

That philosophy matters even more as staffing challenges persist across the industry.

Restaurant turnover has remained above 75% in recent years, and the hidden cost of that churn runs into thousands of dollars per employee once you count hiring, onboarding, and training.

When recipes, techniques, and expectations are thoroughly documented, new hires become productive far faster than when knowledge lives only in the heads of experienced team members, which is exactly the payoff that reducing turnover is meant to protect. Recipe-based kitchen training turns the standard itself into the onboarding tool.

The objective isn't to remove people from the equation. It's to make the organization less dependent on any one individual. When quality is embedded in the system, great people make it even better. They don't become the only thing holding it together.

Standardization Begins Long Before Opening Day

By the time guests taste a finished dish, most of the important decisions have already been made.

The founders of Fish Cheeks don't settle for the first ingredient that works. They keep searching until they're convinced they've found the right one.

Test Until the Variables Disappear

Fish sauce became a year-long exercise in comparison. Brand after brand. Seafood markets. Grocery stores. Repeated tastings. The same process played out with palm sugar. Every ingredient had to earn its place.

Testing Turns a Recipe into a Standard

The bakery demanded even more discipline. Launching Bubs wasn't simply about developing gluten-free recipes. It became a research project.

"We literally saw each other every Friday for two years before we actually opened."

That level of patience rarely makes headlines. But it's what allows a recipe to become something more than an expression of one chef's instinct. Testing by weight. Recording every adjustment. Refining the specification until someone else can reproduce it without guesswork.

That's where recipe development becomes recipe standardization. And it's also where scaling a recipe stops being a gamble, because a spec you tested by weight is a spec you can multiply across a production run without losing the result.

Getting the Standard Out of the Founders' Heads

Every growing restaurant reaches the same crossroads. For a while, the founders are the system. They taste every new dish, answer every question, and catch every inconsistency before it reaches the dining room.

Eventually, growth makes that impossible.

Saesue and Suansilphong know exactly what that transition feels like because they lived it. For years, they were involved in everything. Delegating wasn't simply a management decision. It meant trusting someone else to protect the standards they had spent years building.

That trust didn't happen overnight. It was earned through structure.

"We trust them to run all the restaurants the way we want them to. It took a couple of years, but they're doing a better job than us."

Recipes Become Organizational Memory

The sentence is striking because it reveals what successful delegation actually looks like. The goal isn't finding people who cook exactly like the founders. It's building systems strong enough that talented people can eventually perform even better.

That shift changes the founders' role. Instead of personally maintaining consistency, they become responsible for designing the systems that maintain it.

At Fish Cheeks and Bangkok Supper Club, that system includes clearly defined leadership roles, regular collaboration, and continuous learning. Chef Dustin travels with Suansilphong to Thailand to deepen his understanding of regional ingredients and techniques before bringing those lessons back to the team. Every Tuesday, they taste new dishes together before anything reaches the menu.

Those meetings aren't simply recipe development. They're knowledge transfer.

Every discussion, every adjustment, every tasting is another chance to turn instinct into something the broader organization can understand and repeat. That's the same reason training staff directly from your recipes beats a binder nobody opens: it gives people access to everything the founders have already learned.

Documentation Isn't Bureaucracy. It's Memory.

The more Saesue and Suansilphong describe their process, the clearer it becomes that documentation isn't about paperwork. It's about protecting knowledge.

Restaurants often assume training happens when someone demonstrates a technique. But demonstrations disappear, people leave, and memories fade. Verbal instructions also evolve a little every time they're repeated. Written standards don't.

Recipes Become Organizational Memory

Recipes become the place where decisions are preserved. Not just ingredients and quantities, but sourcing choices, preparation details, production methods, and the reasoning behind each step. That's why a recipe system becomes far more than recipe storage. It becomes organizational memory.

The same principle runs throughout restaurant history. Julia Child believed recipes should teach technique rather than simply list ingredients, and that instinct still separates strong recipe training from weak training. The stronger the recipe, the less dependent the cook becomes on the person who originally created it.

When recipes become living documents instead of static files, the standard becomes portable, and portability is what lets restaurants grow.

Training stops depending on who happens to be working that shift. Every new employee starts from the same foundation.

The Problem Isn't Too Little Data. It's Too Many Places to Find It.

When Saesue talks about the future of restaurant technology, she doesn't start with artificial intelligence. She starts with something much simpler: finding information.

"For all the platforms to live in the same ecosystem, currently, nothing lives together. Everything is like a separate thing. It's still hard to find information and pull information."

Anyone managing a restaurant understands the frustration. Reservations live in one platform. Marketing data lives somewhere else. Recipes sit in another system. Inventory, labor, purchasing, costing, and guest information each occupy their own corner of the business.

Answering a simple question often means opening five different applications. Who's our best regular? Which dishes do they order? Has that recipe changed recently? How has food cost moved? The information exists. It just doesn't exist together.

Restaurant Dive has described the same challenge across the industry. Most operators aren't struggling because they lack data. They're struggling because every system stores its own version of it, forcing people to connect the dots by hand.

That's where meez fits the conversation.

Give Culinary Knowledge One Home

meez isn't trying to replace every operational platform.

It gives the culinary layer a centralized home: the recipes, costing, specifications, and training materials that directly shape what reaches a guest. Instead of living across spreadsheets, binders, PDFs, and individual laptops, recipe knowledge becomes part of one connected operating system.

For founders like Saesue, that's less about technology than clarity. People shouldn't have to remember where information lives. They should simply be able to find it.

Bubs Bakery Proves the System Works

The founders didn't build Bubs Bakery simply because they wanted another concept. They built it to solve a personal problem. Saesue's husband lives with diabetes and multiple food allergies, which made it remarkably difficult to find baked goods he could eat and actually enjoy.

The goal wasn't creating an acceptable gluten-free bakery. It was creating products that happened to be allergen-free because they were exceptional. That's a much higher standard, and it leaves almost no room for inconsistency.

Allergen-Free Recipes Leave No Room for Drift

One undocumented ingredient. One substituted product. One deviation from the recipe. Any of those could break the promise the bakery makes to every customer.

That's why the two years of testing mattered. The recipes weren't simply delicious. They were dependable. Every batch could be reproduced with confidence because every variable had already been challenged, refined, documented, and verified.

Demand for allergen-aware products keeps climbing. The gluten-free bakery segment is growing at roughly a 10% annual clip as more guests seek out these options, which raises the stakes on precision.

When guests trust what's written on the label, recipe standardization stops being an internal process and becomes a promise.

The Better Question to Ask

Restaurant operators often ask, "How do we protect our secret recipe?" Saesue and Suansilphong point to a better question: could your signature dish survive your absence?

Every choice they described pushes knowledge away from individuals and into the organization. That's why they invested years, not weeks, into testing recipes. Why they still taste new dishes every Tuesday. Why they built clear roles instead of expecting everyone to do everything. Why Saesue dreams about pulling disconnected platforms into one ecosystem.

Test Your Own System

So put your own operation to the test:

• If your best chef took a month off, would the quality change?
• Could a new cook reproduce your most important dish from documentation alone?
• When a recipe changes, does every station get the update immediately, or does it travel through conversations?
• Are your recipes just ingredient lists, or do they capture sourcing, prep, technique, and the reasoning behind each decision?

Those questions reveal whether you're protecting recipes or building systems. One creates consistency. The other creates dependence.

The founders of Fish Cheeks, Bangkok Supper Club, and Bubs Bakery didn't build three successful concepts by guarding secrets. They built them by making their standards repeatable.

Recipes can be copied. Systems are much harder to replicate.

Recipe-based training keeps every cook working from the same trusted standard, from day one to year ten. See how meez supports training leaders.

Listen to the full episode: Jenn Saesue and Chat Suansilphong of Fish Cheeks, Bangkok Supper Club and Bubs Bakery on Thai cuisine and how to actually make good gluten free baked goods

What is recipe standardization?

Recipe standardization is the process of documenting recipes so they can be prepared consistently regardless of who's cooking. Beyond ingredient lists, standardized recipes include exact measurements by weight, preparation methods, yields, plating guidance, and operational notes that turn a chef's knowledge into a repeatable system.

How do restaurants maintain consistency across multiple locations?

Consistency comes from a single source of truth for recipes, costs, and training. Rather than relying on printed cards or verbal instruction, successful multi-unit operators distribute updates centrally so every location follows the same current standard at the same time.

How do you scale a restaurant without losing quality?

Saesue and Suansilphong's experience suggests scaling starts long before you open another location. Thorough ingredient testing, documented recipes, clearly defined leadership roles, and repeatable operating systems let teams deliver consistent quality without relying on the founders to oversee every shift.

Why is recipe testing so important?

Testing removes uncertainty before recipes reach the kitchen. Evaluating ingredients, refining ratios, and documenting the final specifications and scaling produces recipes that are both reproducible and profitable, reducing variability while protecting margins.

How does recipe standardization improve staff training?

Standardized recipes become training tools. When methods, visuals, and specifications all live in one place, new employees learn from the same documented standard every experienced cook follows, which shortens onboarding and reduces errors.

Why is standardization especially important for allergen-free menus?

Allergen-friendly products leave little room for improvisation. Every ingredient, process, and specification must stay consistent, because even a single undocumented change can compromise the promise made to guests. That's why Bubs Bakery spent two years refining and documenting its recipes before opening.

What's the difference between a recipe and a kitchen SOP?

A recipe defines how a specific dish is prepared: quantities, method, and plating. A kitchen SOP governs broader operations such as food safety, opening and closing procedures, station setup, and cleaning. Together, they form the operational foundation that lets restaurants scale consistently.