How Zero-Waste Thinking Becomes a Kitchen Training System

Zero-waste cooking can sound like an idea that works beautifully in theory and falls apart during a busy dinner service.

But that's not how Vojtech Vegh approaches it.

Vegh, founder of Surplus Food Studio, works with chefs, hotels, resorts, and large contract catering organizations around the world to reduce food waste. And despite the scale of the problem, his starting point is surprisingly simple.

When Josh Sharkey asked him on The meez Podcast what he actually teaches chefs, Vegh made an important distinction:

"I don't teach chefs how to cook. They know how to cook. That's not my work. It's seeing the possibilities with everything that is currently in your bin, but shouldn't be."

What is zero-waste?

The problem usually isn't that chefs lack the skill to turn watermelon rind, pineapple skins, yesterday's bread, or vegetable trimmings into something useful. It's that kitchens have spent years treating those things as waste.

Vegh's work is about changing that instinct: helping chefs look at what normally goes into the bin and ask, What else could this become?

But changing the way one chef thinks is only the beginning.

For zero-waste cooking to have a meaningful impact across a restaurant, hotel, or hundreds of kitchens, that way of thinking has to become part of the operation. Teams need to know what can be reused, how to use it safely, and how to make those practices repeatable even when the chef who introduced them isn't there.

That's where zero waste stops being a philosophy and starts becoming a system.

The First Step Is Measuring What Everyone Else Ignores

One reason Vegh's work resonates is that it begins with evidence instead of ideals.

When Josh asked which ingredients are wasted most often in professional kitchens, Vegh didn't offer guesses. He offered data.

What is the most wasted ingredient?

Across the operations his team measures worldwide, watermelon rind ranks first by trimming volume, representing roughly a quarter of the fruit.

Next comes pineapple skin, heavy and still carrying a lot of attached flesh, followed by bread and rice, particularly in Asian markets where rice is produced in volumes that virtually guarantee leftovers.

Those rankings matter because they replace assumptions with measurement.

Vegh isn't interested in making kitchens feel guilty about waste. He wants them to understand where waste actually occurs.

How concerned is the restaurant industry?

The wider industry is beginning to move in the same direction.

According to the National Restaurant Association's 2026 State of the Restaurant Industry report, more than a third of operators increased food waste tracking or adjusted portion sizes over the past year.

ReFED has reported the same shift from the other side, noting that margin pressure and high food prices have made a problem operators once treated as invisible considerably more visible.

Vegh's credibility isn't that he loves scraps. It's that he counts them.

When Does Reasoning Disappear?

On the podcast, Josh asked Vojtech if there was one phrase he'd eliminate from professional kitchens forever. He answered without hesitation: "We've always done it this way."

His response wasn't about resisting tradition. It was about questioning habits nobody remembers creating.

When someone tells Vegh they've always done it this way, he sees something deeper than reluctance to change. He sees a kitchen operating on inherited behavior instead of deliberate standards.

Somewhere along the way, someone made a decision, and that decision became routine.

Eventually, nobody remembered why the habit survived.

That's a problem far bigger than food waste. It's how organizations lose knowledge.

Undocumented habits

If the current standard exists only because the previous person followed it, then you've stopped using reasoning.

No one has documented it or tested it for efficiency. It was just decided to remain the best approach.

Vegh isn't criticizing the people working in those kitchens. He's exposing a weakness in the system. Habits aren't documentation because memory isn't a standard.

You Can't Train Someone to Notice What They Can't See

One of the biggest challenges Vegh encounters has very little to do with cooking.

It's scaling awareness.

Teaching one chef to rethink food waste is easy enough. But teaching hundreds of cooks across an organization to make those same decisions every day, without the person who taught them standing beside them, is something else entirely.

Vegh is clear that this is where most training programs reach their limit.

A workshop can change one person's perspective, and a masterclass can inspire a team. But neither guarantees that the next hire will work the same way six months later.

That's the reality restaurants are operating in today.

Write it down

Toast reports annual restaurant turnover of roughly 78 percent, and that reporting makes a point Vegh would recognize: hiring faster doesn't solve it, because kitchen workflows and daily routines are difficult to learn in the first place.

Cornell research puts replacement costs at about $5,864 per employee, and nearly three-quarters of operators say they expect to keep hiring while struggling to find experienced managers and chefs.

Vegh doesn't see hiring as the solution. Waiting until someone arrives with the right mindset isn't a strategy.

Instead, he advocates something much less glamorous: write it down.

Once a watermelon rind has a documented prep method, a yield, and a place inside a recipe, success no longer depends on someone remembering that it could be used. The station simply follows the standard. Kitchen training stops relying on instinct and starts relying on systems, which is also what makes it repeatable for every hire after that.

“A chef's insight becomes an organizational habit. And organizational habits survive turnover.”

The Most Expensive Thing You'll Throw Away

One of Vegh's most valuable observations came while talking about bread.

Not because bread is particularly expensive to buy, but because it's expensive to make.

"For those kitchens that make homemade bread, it's one of the most expensive things that they are wasting, because of the labor, space, and equipment that goes into making that bread that eventually ends up in a bin."

That's a different way of thinking about waste.

Most kitchens calculate the cost of discarded food by looking at the invoice. Vegh looks at everything that happened afterward.

The labor, space, and equipment are the expensive part

By the time a loaf reaches the bin, the flour itself is almost irrelevant. The investment is what matters.

He illustrated the same principle with a story from his own career.

Working in a fine-dining kitchen with prep upstairs and service downstairs, he left a large reduction going before heading down for service. He got busy.

Service stretched on. By the time he returned, months of aging, grains, legumes, expensive seasonings, and several thousand dollars of ingredients had become a ten-centimeter block of charcoal at the bottom of the pot.

Then, unbelievably, he burned the second batch too.

He kept his job. He was not allowed to reduce sauces unattended again.

Kitchen waste isn't measured only by what ingredients cost. It's measured by how much work has already been invested in them.

ReFED estimates that restaurants generate 11.4 million tons of food waste annually, representing roughly $25 billion in lost value, while investments in waste reduction can return as much as $8 for every dollar spent.

That same research found much of the loss comes not from dramatic mistakes but from everyday operational habits.

Turning Waste Into an Ingredient Changes More Than the Menu

When Vegh demonstrates how to transform banana peels into something resembling pulled pork, it's tempting to focus on the technique.

The preparation itself is surprisingly simple. Remove the woody ends. Cut the peel into shorter lengths so the fibers remain pleasant to eat. Shred it. Then braise it with onion, garlic, tomato, and soy.

The chefs tasting it often don't believe what they're eating.

But the real lesson isn't the recipe. It's what happens operationally once that recipe enters a professional kitchen.

The peel is no longer waste. It's now an ingredient.

And once that happens, the kitchen has to treat it like one:

• Document how it should be prepped
• Measure the usable yield
• Account for the labor and true cost involved
• Track it within prep loss and sub-recipe structures
• Define where the ingredient can — and shouldn't — be used

The moment a scrap becomes usable, it also needs a process

Without those pieces, the peel may appear on a plate, but it never really becomes part of the restaurant's operational data.

That single change creates a chain of new requirements. It needs a documented prep method, or the next cook leaves the fibers too long. It needs a measured yield, because peel to finished product isn't one-to-one. It needs a cost, which is now mostly labor. And it needs a place in the prep loss and sub-recipe structure, so the trim stops being invisible and starts being a number.

Vegh thinks this way naturally. He also understands where the boundaries belong.

He advises against using pineapple crowns because of concentrated bromelain and potential allergy concerns. He avoids mango and papaya skins for guests who may be unfamiliar with them. He discourages using avocado skin because agricultural residues can remain on the thick surface, where peeling doesn't help.

Those decisions aren't personal preferences.

They're operational standards.

Once they're documented, anyone can follow them. Left inside one chef's memory, they're almost impossible to scale.

A Better Recipe Library Helps Chefs Find More Opportunities

The real advantage isn't one clever use for stale bread. It's being able to find every place that idea could work.

One of the most transferable ideas Vegh shares has almost nothing to do with a specific ingredient.

It's about patterns.

Consider stale bread. Instead of asking what single recipe he can make with leftover bread, Vegh asks a broader question:

Where else on the menu do flour and water already exist?

Béchamel. Macaroni and cheese. Casseroles. Cake sponge. Cheesecake crusts.

Boiled and blended bread can replace or supplement the thickening agent in any of them.

The insight isn't one clever recipe. It's a method for discovering many of them.

That becomes much easier when recipes are structured in a way that makes those patterns visible.

A folder full of PDFs can't easily answer a question like, "Show me every recipe using flour and fat." A standardized recipe library can.

That structure makes it possible to:

• Search recipes by ingredient or component
• Find repeated techniques across the menu
• Identify where surplus ingredients could replace something else
• Turn one chef's discovery into an idea the rest of the team can reuse

Vegh is equally practical about implementation.

He consistently favors solutions requiring the least additional labor because he knows complicated ideas rarely survive the pressure of a busy service.

The chef may discover the pattern.

The system is what allows everyone else to find it again.

Simple Ideas Still Need Systems

One thing becomes clear after listening to Vegh: he doesn't believe zero-waste cooking is especially complicated.

"It never looks like it at the beginning, because it feels like it's this big operational hurdle that we need to overcome and solve. But in fact, food waste prevention in zero waste cooking is super simple."

He's probably right.

The techniques themselves often aren't difficult. Save the watermelon rind. Repurpose stale bread. Track prep loss. Question a habit that no longer makes sense.

What makes those ideas difficult is repetition.

The hard part isn't learning a better way. It's making sure the kitchen still follows it three months later.

A chef may leave a workshop inspired. Three months later, during a busy Friday service, the team will naturally fall back on familiar habits unless the better approach has become part of the kitchen's normal workflow.

That's why Vegh's work isn't ultimately just about sustainability.

It's about operational design.

And it's why his philosophy aligns so naturally with recipe management. A recipe isn't simply a list of ingredients. It's one of the places where a better way of working becomes repeatable.

• Yields make waste measurable. Track how much usable product actually comes from an ingredient.
• Prep specs make judgment repeatable. Give every cook the same standard to follow.
• Recipe updates preserve the improvement. Change the process once instead of reteaching it every shift.
• Shared documentation keeps knowledge from walking out the door.

A documented yield turns trim into measurable inventory. A prep specification turns individual judgment into a shared standard. A recipe update means the next cook starts where the last one finished instead of rediscovering the lesson from scratch.

Mindsets inspire change, but systems preserve it.

What Is Your Kitchen Still Trained Not to Notice?

Most kitchens ask how to reduce food waste.

Vegh's perspective suggests a different question:

What valuable things is your team still trained not to notice?

That question reaches much further than sustainability. It applies to training, recipes, prep, inventory, and culture.

It's worth asking:

• What does your team throw away because that's simply how it's always been done?
• If your most experienced chef left tomorrow, which better habits would leave with them?
• Which standards still live inside someone's head instead of your kitchen documentation?
• Do your recipes explain how the kitchen should work, or just list ingredients?

Those questions reveal whether a kitchen is preserving knowledge or constantly rebuilding it.

Because every operational improvement follows the same path.

Someone notices something. Someone proves there's a better way. Someone teaches it to the team.

Then the organization either turns that knowledge into a system, or eventually loses it.

meez helps culinary teams turn recipes, prep methods, yields, and kitchen standards into living documentation, so every new hire inherits the same way of working rather than just the same ingredients. See how it works for culinary leaders.

Listen to the full episode: QuickFire: Chef Vojtech Vegh

FAQ

What is kitchen training?

Kitchen training is the process of teaching cooks to execute recipes, preparation methods, yields, food safety procedures, and station standards consistently. The most effective training relies on documented systems rather than verbal instruction, allowing every cook to work from the same operational standard.

Why doesn't culinary training last?

Because much of it remains person-to-person knowledge. When a technique exists only in someone's memory, it disappears when that person leaves. With restaurant turnover averaging near 78 percent annually, documenting recipes, prep methods, and SOPs is what turns individual expertise into organizational knowledge.

How can restaurants reduce food waste?

Vegh recommends starting with measurement. Track what is actually being discarded, identify recurring sources of waste, and convert usable trim into standardized ingredients with documented prep methods, yields, and recipe applications. Waste reduction becomes durable when it's built into everyday operations rather than depending on individual awareness.

Why is prep loss important?

Prep loss measures the usable portion of an ingredient remaining after trimming, peeling, butchering, or cooking. Understanding yield helps kitchens calculate true food cost, identify unnecessary waste, and cost recipes accurately. meez explains the method in its guide to yield testing.

Which ingredients are most commonly wasted?

Based on Vegh's measurements across a global client base, watermelon rind ranks first by trimming volume at roughly a quarter of the fruit, followed by pineapple skin because of its weight and attached flesh, then bread and rice. Those rankings help kitchens focus improvement efforts where they'll have the greatest impact.

How should kitchens track food waste?

Track waste where it occurs, categorize it by cause such as trim, spoilage, overproduction, or plate waste, then compare actual usage against what recipes say should have been used. The gap between theoretical and actual usage highlights the operational habits creating unnecessary loss. meez covers the approach in its guide to inventory and recipe data.

Are all fruit and vegetable trimmings safe to use?

No. Vegh specifically cautions against pineapple crowns due to concentrated bromelain and allergy risk, against mango and papaya skins for guests unaccustomed to eating them, and against avocado skin because agricultural chemical residue remains on the thick surface. Any expanded use of trim should be documented alongside food safety and allergen guidance.

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

A recipe explains how to prepare a specific dish, while a kitchen SOP defines broader operational processes such as prep workflows, storage, sanitation, and handling procedures. Together they create a consistent operating standard that supports both quality and training.