The shouting head chef has been part of how we picture kitchens for decades: on television, in memoirs, in the stories about what running a kitchen means. And the picture doesn't survive for nothing. When there is nothing written down to lean on, what you have left is your voice.
I'm not writing about bad chefs, but about a trap that catches chefs, cooks, owners and whole teams. Nobody designed it, and everybody keeps it going. The chef who shouts is usually not cruel. He is overloaded, nobody taught him how to lead people, and he works in a kitchen that was never set up to help him. The cook who puts up with it is not weak. She is talented, badly paid, and stuck in a place that values how much she can take rather than how much she grows.
Once you understand the trap, you can build something better. Not softer, better: a kitchen where people know how things are done and are glad to stay.
If someone in a kitchen has to shout to keep order, it means the order hasn't been set up yet. That isn't a verdict, just a place to start.01 — The Cost of Fear
What Everyone Loses
When fear sets the tone in a kitchen, everybody pays, not just the cooks. The chef pays in tiredness, correcting the same things night after night, because the team is learning how to avoid punishment, not how to master the craft. The owner pays when trained people leave and take everything invested in them along. The guest pays when a dish is excellent on Thursday and average on Saturday, because a different cook was on the station and nobody wrote down how it should look.
A cook who is afraid doesn't ask. They hide mistakes, because getting caught feels worse than letting something bad go out. They don't try anything new, because that takes being allowed to fail, and in a kitchen full of fear a mistake isn't a lesson, it's a humiliation. And they don't stay. They leave as soon as anything else turns up: another kitchen, a warehouse, delivery. Anything, as long as they don't dread the alarm clock in the morning.
I have seen the same story many times. A talented chef takes over, brings energy and skill, and runs the kitchen the only way he knows: by being there and by being loud. The first months look good. But by month six the best cooks are gone. They usually leave first, because they have somewhere to go. By month twelve, only those who feel they have nowhere else are left. The chef, surrounded by people who stay out of necessity, shouts even louder. To him it looks as if others have failed, when really it's the way of working that has failed.
From what I have seen, in kitchens that correct through fear, people stay four to six months. Where the standards are written down and mistakes are talked through calmly, they stay fourteen to twenty-two months. That's the difference between endlessly training new people and having a team that grows together.
02 — The Root CauseWhy This Happens — an Honest Look
Chefs who shout rarely do it because they're bad people. They do it because their circumstances make shouting look like the only option. Here are those circumstances, one by one.
That's how they were taught. In the brigade they came up in, the voice was how you led. The chef who taught them shouted, and so did the chef before him. It gets passed down like a family recipe, except hardly anyone questions this one, because it would feel like betraying the person who taught you. Many chefs have never seen it done another way. They aren't choosing shouting over something else, they're doing the one thing they know.
The pressure is real. A full house, a broken oven, a cook who didn't prep enough mise en place: nobody is imagining that stress. Saturday, 7:45pm, 80 covers on the book and one burner down. Wanting to shout at that moment is completely human. But precisely because the pressure is real, it's worth preparing for it, so that the 7:45 crisis doesn't happen, or so that everyone knows what to do when it does.
Nothing is written down. This may be the most important one. When a recipe exists only in the chef's head, the only way to correct someone is to tell them, often loudly, on the spot and in front of everyone. The chef doesn't want to humiliate anyone, he reacts in the moment. If the standard were written down, pinned up and practised, the correction wouldn't be personal. "Check the card" is a calm sentence. A raised voice in the middle of service is making up for what was never written down.
Urgency and aggression sound alike in the rush. "Fire table 7, two lamb, one fish" is urgent, and it should be. "Where's my lamb?" said in anger is something else. Same kitchen, same pressure, and a very different effect on the person hearing it. Urgency is the rhythm of service and it belongs there. Aggression is a habit, often unintended, that builds up and teaches the team that this isn't a safe place. The line between the two is thin and easy to lose if you're not paying attention.
The money doesn't add up, and everybody feels it. Under everything else is money, which this trade doesn't like to talk about. Line cooks have been underpaid for years. In much of the region a cook barely covers rent and food: feeding others while struggling to feed yourself. Prices go up and kitchen wages stay put, so a cook on the same pay today earns less than three years ago. Management pays the chef enough to demand results, but doesn't invest enough in the team to bring in and keep the people who can deliver them. The chef is left with high expectations, low wages and a door that keeps revolving. When he can't motivate with fair pay, it's easy to start motivating with pressure and end up enforcing someone else's cost-cutting. That isn't the kitchen failing, it's the business model, and the kitchen takes the consequences.
03 — The Ego TrapWhen Identity Gets Tangled in the Plate
Something happens to cooks that doesn't happen in most jobs: the work becomes personal, and that's hard to prevent. You spend years building technique, palate, instinct, and at some point the food stops being something you make and becomes something you are. The plate becomes part of you. That's where the trouble starts.
When the plate is part of you, a bad plate hurts as if you were bad. A ruined sauce isn't a mistake in the process, it's a personal defeat. And when a cook on your team ruins that sauce, your first thought isn't "something went wrong in how we work", it's "he disrespected what I want". The correction that follows comes from hurt, not from a clear head. And hurt people don't teach well. They react.
That isn't a character flaw. It's a trap the trade itself built. We celebrate chefs as artists and put their names on menus and their faces on screens. We tell them: this food is you. Then we're surprised when they take every mistake personally. We built the stage and then blame the actor for acting.
A chef like that is often the most dedicated person in the kitchen: first in, last out, and he cares about every gram, every degree, every plate that leaves the pass. That care is real. But when it has nowhere to go, when there are no written standards, no regular talk about the work and no clear line between "the dish didn't work" and "you let me down", it turns inward and then comes out as anger at whoever is closest.
It's worth asking: does the correction teach, or is it a show? "This needs more acid, taste it and fix it" is a chef solving a problem. "Who put this on the pass?", said so the whole line hears, is a chef trying to get back a sense of control. Both times the chef cares about the food. But after the first, the cook gets it right next time. After the second, the cook hides the mistake next time.
The way out isn't to care less. It's to write the standard down: on the recipe card, in a photo, in a written procedure for the station, so it doesn't live only in your head and heart.
Once the standard is written down, the chef doesn't have to guard it alone. He has time to teach people, and the food gets better for it.04 — The Exception
When Raising Your Voice Is the Right Thing to Do
To be completely honest: there are moments in service when a raised voice isn't abuse, it's a tool. You use it on purpose, and briefly.
A cook drifts. It happens. The body is at the station and the head is somewhere else: a fight with a partner, a bill they can't pay, a message that arrived at the wrong moment. The hands slow down, the eyes glaze over, the timing starts to come apart. In service that doesn't only hit the cook, it hits the whole line. The stations work together, and when one slows down, they all stall.
Then a sharp call, not an insult and not a humiliation, but a clear, loud signal, can do what a tap on the shoulder can't. It cuts through the noise and brings the attention back to the pan and the ticket. Like a splash of cold water: sudden, short, and it works.
That's not the same as shouting at someone because you're angry. The difference is in the intent, the length and what comes after. A call like this lasts three seconds and carries information: "Behind you, fire table nine, now." There's no judgement in it. The cook hears it, pulls themselves together and gets back into rhythm. Half a minute later nobody even remembers it, because it wasn't personal. It was loud only because, at that moment, a loud voice was the one thing that could get through the fog.
Experienced chefs know that moment, and plenty of cooks have been grateful for it: a sharp voice pulled them back just before they burned the reduction or missed a ticket. That isn't cruelty, it's attention. The chef reads the kitchen and the person and picks what helps, not what makes him feel powerful.
I mention this because it would be naive to pretend it doesn't exist. I'm not saying a kitchen should be silent, but that the voice should be used rarely and accurately: to get the cook's attention back, not to let the chef blow off steam.
When you raise your voice to bring back focus, that's leading. When you raise it to shame someone, that's something else, and you have to tell the difference in the middle of service, not afterwards.05 — The Alternative
Order That Makes It Easier for Everyone
In a kitchen that's in order, the load that used to sit on the chef alone is carried by what's written down. When the recipe is written to the gram, when each station has a setup checklist and everyone knows what they're responsible for, the chef is no longer the only one guarding quality.
Correction then becomes shared work, not a fight. "Your yield on that cut was 62%, the target is 70%. Let me show you again" is a conversation about the standard, not about the person. It doesn't hurt or shame, and the cook improves instead of hiding.
That isn't soft leadership, it's exact leadership. And every chef already knows exactness, because he applies it to food every day. Someone who can taste a sauce and tell it's missing half a gram of salt can also write the work down so the next cook gets it right without being corrected. Same skill, used somewhere new.
An example. In one kitchen I worked with, the chef de partie was constantly being corrected on plating, because the look of the plate existed only in the head chef's mind. We wrote down every dish, with a photo, measurements and a step-by-step method. Within a week there were far fewer corrections. The chef de partie hadn't got better overnight, he finally knew what "right" looked like. The frustration didn't stop because someone became more patient, it stopped because its cause was gone.
Another example. In one kitchen the sauces were never consistent: the same dish tasted different depending on who was on the station. Until then the fix had been for the chef to taste every sauce himself and correct the cook on the spot. We wrote down the base sauces with exact measurements, reduction times and a description of what each sauce should be like. Within two weeks the differences had almost disappeared. The chef no longer had to police the station, and the cooks no longer had to guess.
When the work is written down, the chef isn't made redundant. He has time to lead, teach and think ahead, instead of spending the day correcting the same mistakes.06 — The Five Shifts
From Volume to Order
From spoken instructions to written standards. A standard that exists only in someone's head is really that person's preference, and preferences change with mood, tiredness and the Saturday rush. A recipe card, a plating photo, a prep list aren't bureaucracy. They are what keeps a dish the same from day to day, so the chef doesn't have to remember everything and the cook doesn't have to guess.
From correcting the person to correcting the work. "The standard says X, we got Y, let's see where the gap is" is a conversation about the work. "You always get this wrong" is a verdict on the person. Both chefs want a better result. But the first makes the cook better, and the second just makes them defensive. The difference usually isn't in the intent, it's in whether there's something written down you can point to.
From how much you can take to how much you know. A kitchen that values "this week I learned to break down a lamb shoulder" more than "I worked a double on Saturday" is a kitchen where people grow. Endurance has its place, this is physically hard work. But endurance without progress just does damage more slowly. The point is to get better in the kitchen, not only to survive it.
From unclear to clear. Everyone on the team should be able to answer three questions: What is my job? What am I responsible for? How do I know if I'm doing well? If they can't, it isn't their fault, it's how the kitchen is set up, and the frustration that follows usually comes out through the chef. When things are clear, there are fewer fights.
From putting out fires to planning. A short briefing before service, a daily prep list, a weekly review. A lot of kitchen chaos can be prevented with five minutes of planning that many kitchens skip because everything feels urgent. And five minutes of talking before service saves half an hour of confusion during it. The resistance is rarely practical. It's more a habit, the belief that a real kitchen always copes somehow. But it's better to prevent the chaos than to be good at coping with it.
07 — The Price TagWhat the Trap Costs — in Euros
Some people aren't moved by talk about the team's wellbeing. For them I use the language of money, because numbers, once you line them up, are hard to ignore.
A line cook in the region costs between €600 and €1,200 a month. Training them on a specific menu, not just techniques but the standards, timing and plating, takes at least six to eight weeks. In that time, by my estimate, they do roughly 40% of what a trained cook does. They're learning, and the kitchen covers the difference.
Then that cook leaves, pushed out by frustration, the atmosphere and the feeling that the effort isn't worth it. The position stays empty for two to four weeks. Everyone works more. Overtime piles up, sometimes paid, more often swallowed in silence, and that wears people down too. Quality drops on the empty station. Sometimes covers are turned away, because a kitchen with a gap on the line can't handle a full book.
Then a new cook arrives, and it all starts again.
When I add it all up, finding someone new, lower output while they learn, the others' overtime and uneven quality, by my calculation replacing one line cook costs roughly €3,800 to €6,200. A kitchen that loses four cooks a year loses €15,000 to €25,000 that way. And those are today's prices. Food, energy and rent keep going up, so these numbers will grow too. A place already running on thin margins can't take a loss like that for long. But most owners don't see it, because it isn't on any invoice. It's spread across months of weaker work, and only someone looking for it will notice.
What never shows up on any report is the knowledge walking out the door. A cook who leaves after eight months takes eight months of learned timing, little things about who likes what, memorised allergies and polished technique. A recipe card alone doesn't replace that. It's two hundred and forty shifts in which a person learned the rhythm of that particular kitchen, and it all goes when they untie their apron for the last time.
When an owner keeps a way of running things that drives people out, because the food is good, because change feels risky, because "that's how kitchens work", he's making a financial decision, even if he doesn't see it that way. He sees the plate, not what is slowly being lost underneath it.
The trap is expensive, and the longer it lasts, the more it costs: in money, in people, and in what those people could have become.
The knowledge that leaves with a cook can't be hired back. It can only be built again, slowly, if someone stays long enough.08 — The Generational Shift
Younger Cooks Want Clarity
Older chefs often repeat the same story: the new generation is soft. They can't take pressure, they want days off, they want praise, they don't understand what this job demands.
It's a comfortable story, and mostly wrong.
Young cooks aren't softer, they're used to something different. They grew up at school, online and in a society where the rules were mostly clear and written down. They expect clarity not because they're fragile, but because they know what it looks like. A twenty-two-year-old who asks "what exactly do you want this to look like?" isn't being difficult. They're asking one of the most professional questions a cook can ask. If that annoys the chef, it says more about how his kitchen is set up than about the cook.
The paradox is that this "soft" generation does better in an organised kitchen than many before it. They're used to written instructions and checklists, and they respond well to clear feedback and standards you can measure. In a word, they're orderly, and no kitchen runs well without order. The problem isn't that they can't handle the work. It's that the work has no order for them to hold on to.
But there's something deeper, and it starts above the kitchen.
Budgets tighten every year and expectations rise. More covers, more complicated menus, Instagram plating that takes longer per plate, and the staff budget stays flat or shrinks. Management wants more from fewer people. The chef takes that pressure and passes it down, and the cook either puts up with it or leaves. And when they leave, the story is almost always the same: "they couldn't hack it." Rarely: "we didn't invest in them."
This is where the trade isn't honest with itself. We ask people to give their best while paying them barely enough to live. We expect loyalty from people we treat as replaceable. We demand passion from people whose exhaustion we refuse to see. And then we say: the new generation doesn't understand hospitality.
They understand it very well. Well enough to leave.
I think the kitchens that will do better over the next ten years are the ones that see this change as a chance, not a threat. Young cooks who like order will build with you, if you give them an order worth building on. If it's safe to ask questions in your kitchen, their questions will improve the way you work. And they'll stay if you treat them like people. That isn't a concession. It's an advantage many in this trade haven't noticed yet.
And to the managers and owners reading this: the chef isn't the only one who needs to change. If your business only survives because people work unpaid overtime, it's the business model that's broken, not the staff. The chef at the pass can write down and organise everything, but if the people above him see the team as a cost to cut rather than people to invest in, it won't last long.
A kitchen that gives young cooks clear rules instead of stories about the old days will keep them more easily than one still running on fear.09 — What They Carry Home
The Kitchen Follows You Out the Door
Almost every cook knows this moment. Service ends, the last plate goes out, and you step out into the night. It's late, the street is quiet, your hands smell of garlic and fryer oil. And somewhere inside there's a tension that won't let go, not straight away, sometimes not for hours.
People outside this work find it hard to understand what a cook takes home. I don't mean physical tiredness, that's obvious and in a way honest: the body worked and the body is tired. What's harder to describe is what stays in your head: a correction that hurt, a rush you haven't digested yet, the feeling that you gave everything and you're not sure it was enough.
In kitchens where the work is in order and people talk with respect, you can carry it. You go home tired but whole. You sleep, recover, come back. In kitchens where corrections come with contempt and mistakes are met with humiliation instead of explanation, it piles up and gets heavier.
Anyone who has spent time in this work will recognise it. The cook who can't sleep. The sous chef whose relationships outside the kitchen keep falling apart. The chef de partie whose anxiety arrives on Tuesday and doesn't leave until Monday, because the body remembers service even when the head is trying to rest. These aren't signs of weakness. They're signs that the kitchen asks too much and gives back too little.
The trade likes to romanticise this. "I survived Chef So-and-So's kitchen" gets said with pride. And there's something real in that pride: you held on, you passed the test. But holding on in a kitchen that wears people down isn't the same as growing. It's survival, and over the years survival has a price that hardly anyone admits until they've paid it.
A cook leaving after a shift tired, but not smaller than when they came in, should be the minimum, not a dream. A kitchen like that needs order, yes. But it also needs something simpler: understanding that the people who cook aren't fuel. They are the kitchen, and they deserve to go home whole.
I don't judge a kitchen only by the plate, but also by the state the people who made it are in when they go home.10 — The Result
Quiet Kitchens Cook Better
The best kitchens I've worked in, and the ones I've helped put in order, were quiet. Not silent, quiet. People speak briefly and clearly, everyone knows where they're going, the attention is on the work. Nobody raises their voice, because there's no need when everyone knows how things are done.
That doesn't mean nothing goes wrong. Something always goes wrong. A cook drops a pan of reduction, a plate comes back, the oven dies mid-service. The difference is in how you react. In a quiet kitchen the questions are practical: What broke? How do we make up for it? Who takes over what? The cook who dropped the reduction gets help making it again. The table gets its food a few minutes late. The team goes home at the end of the night tired, but whole.
I remember a service when exactly that happened. A cook dropped forty-five minutes of work on the floor. Earlier on, in that same kitchen, that would have set off an explosion. This time the sous chef just recalculated: "Table 12 moves eight minutes. I'll start the reduction. You re-fire the protein." No drama, no blame. The guests at the table never found out. And the cook learned that in that kitchen a mistake is a problem to solve, not a crime to punish.
That's what you get from a kitchen that's in order: not perfection, but being able to take a mistake and carry on without everything falling apart. A kitchen that gets through a dropped pan without shouting is stronger than one that runs flawlessly while it's calm and falls apart the moment something breaks.
You see a kitchen best when something goes wrong: how it reacts, and how the people are afterwards.11 — The Balkan Kitchen
How It Is Where We Are
Everything so far applies more or less everywhere. But the Balkan kitchen has its own weight, its own inherited habits and its own way of confusing toughness with tradition.
Here, the hierarchy in a kitchen isn't only about the job, it's also cultural. The older one leads, the younger one listens. When a younger cook questions an older one, it's rarely seen as initiative and more often as disrespect. A chef who keeps the kitchen in a firm grip through volume and pressure isn't seen as someone who lacks the tools to lead people. He's seen as "strict", and here that's a compliment. The people around him reward it, and very few have the words or the nerve to say what is really going on.
Then there's how we show feelings here. In many kitchens in the region, admitting you're struggling means showing weakness. A cook who says "I need help" risks losing face, and a cook who shows emotion risks being written off. So the pressure goes under the surface and comes out where it's harder to see and harder to treat: in tiredness nobody talks about, in tension people take home, in quietly accepting that this is the price of the job.
Then there's the job market. In much of the region cooks have fewer options than colleagues in Western Europe. When the alternative is unemployment or a kitchen with the same problems, whoever is hiring holds all the power, not because of anyone's talent, but because of geography and economics. People stay because they can't see where else to go, not because they're doing well. That isn't loyalty, it's the same trap under another name.
And under all of that is what gets handed down. A chef who learned the trade in the nineties learned it from someone trained in the eighties, who learned in Yugoslav hotel kitchens where military discipline was the model and questioning wasn't the custom. Three generations of the same habit, each one thinking it's keeping the standard when it's really keeping a pattern nobody stopped to look at. One workshop isn't enough to break that chain. It takes someone, ideally from inside that tradition, to look honestly at what they inherited and say: we keep what works and let go of what doesn't.
I say this as someone who comes from that tradition and was shaped by it. In my first years I carried parts of it forward without thinking, because the kitchens I respected worked the same way and I didn't yet know another way. Understanding that something had to change came slowly, one person at a time, as I watched talented people leave because the kitchen didn't let them grow. Each of them taught me something. Some of those lessons came later than they should have.
The Balkan kitchen has a lot going for it: the ingredients, the culinary heritage, and talented people who grew up around food many Western European chefs would envy. It doesn't need imported solutions. It needs order built here, from the inside, where the craft is learned without using people up, where they grow instead of being ground down. That's how this region will get the kitchens it's capable of.
Tradition isn't something to throw away. It's something to look at honestly, respecting what it built and being clear about what it cost. What helps people, we keep. What wears them down, we do differently.12 — The Challenge
For Every Chef Reading This
Try it for one week, that's all. For one week, say every correction in a normal voice. Not because passion is wrong or urgency has no place in a kitchen (you've read the exception, you know the difference), but to see what shows up. Five services, a normal voice, and a notebook in your pocket.
Every time you want to shout and don't, write it down. Not what you felt, but what happened. What was missing? What, if it had been written down or agreed beforehand, could have prevented that moment?
At the end of the week, look at that list. You won't see a list of bad cooks, you'll see a list of gaps in the way you work. And gaps can be closed, one at a time: with a recipe card, a checklist, a short briefing before service, clearly divided roles.
This isn't about becoming a softer chef, but a smarter one. A kitchen that runs on agreed order isn't weaker than one that runs on fear. It takes knocks better, the food is more consistent, and it's far more likely to still be open in three years with the same team that opened it.
If something in this text bothered you, stay with it for a moment. Change usually starts with that kind of discomfort, and it starts with you, not with the person next to you.
If you want to see how I work, it is all written down in the methodology. Or get in touch.