Pressure vs. Abuse: What Every Brigade Must Know

bullying

I once watched a senior sous chef throw a ladle at the pass because a commis had seasoned a bisque incorrectly. Not thrown it down in frustration. Thrown it. At a person. The commis was nineteen, it was his third week, and he went home that evening and handed in his notice by text. We lost him. Good lad, actually. Quick hands, good palate, would have made something of himself. And that sous chef? Carried on as if nothing had happened, because back then, nobody said a word.

That was the kitchen I came up in. I’m not proud of it. But I think about it often, especially now, when I talk to young chefs who are genuinely uncertain whether what they’re experiencing is normal professional pressure or something that ought to have a name and a consequence attached to it.

This matters. Not because kitchens have gone soft, or because we’ve lost our edge, but because there is a real and important distinction between the two things. And if you’re running a brigade, at any level, you have a responsibility to understand it.

The Pressure Is Real, and That’s Fine

A professional kitchen is a high-pressure environment. It always will be. Service is live, the food is perishable, the timings are unforgiving, and a hundred small decisions get made every thirty seconds. There is no pause button. When a section falls behind, it affects every other section. When someone misreads a ticket, a table of eight waits longer than they should, and the chef who plated the wrong garnish hears about it. Clearly and immediately.

That is pressure. That is the job. The ability to absorb that pressure, to stay organised and precise in the middle of it, to take a sharp correction and apply it rather than unravel, is exactly what separates a capable cook from someone who is still learning. You don’t build resilience without discomfort. Nobody ever improved by being told everything was wonderful when it wasn’t.

I have raised my voice during service. I will not pretend otherwise. When a sauce breaks five minutes before it goes to the table, or when someone plates a dish they knew was wrong and hopes nobody notices, a calm, measured response is not always what comes out. It shouldn’t have to be. Standards matter. The correction matters.

Where It Goes Wrong

The problem is when pressure stops being about the food and starts being about the person. There’s a difference between “that sauce is under-seasoned, taste it again and fix it” and “you’re useless, you’ve always been useless, I don’t know why I bother.” One is a correction. The other is an attack on someone’s worth as a human being. That distinction is not subtle. It’s enormous.

Abuse in a kitchen rarely arrives as a single dramatic incident. It tends to accumulate. It’s the constant belittling, the mockery in front of the whole brigade, the deliberate exclusion, the screaming that goes beyond the moment and becomes personal. It’s the chef who picks one person to humiliate every service, not because that person makes more mistakes than anyone else, but because they can. Because nobody stops them.

And here’s the thing that nobody talks about enough: abusive behaviour in a kitchen does not produce better food. It produces frightened cooks who stop asking questions, stop flagging problems, and start hiding mistakes. Which is the worst possible outcome for a restaurant that cares about what it sends out.

Teaching the Difference to Your Team

If you’re a head chef or a senior cook, this falls partly on you. You set the culture, whether you intend to or not. The brigade watches how you behave under pressure, and they take notes. So here are some things worth being clear about, with yourself first, and then with the people you work alongside.

  • Corrections should be specific and about the work. “This beurre blanc has split because the heat was too high, here’s how you bring it back” is useful. “What is wrong with you” is not. One teaches something. The other just damages.
  • Volume is not the same as seriousness. You can raise your voice in a busy kitchen and still be fair. What matters is whether the words you’re using are about the mistake or about the person.
  • Repetition without support is abuse. If someone keeps making the same error, screaming at them again is not a management strategy. Show them. Explain it differently. Find out if there’s something they haven’t understood. That’s your job as a senior cook.
  • Silence is complicity. If you watch a colleague being humiliated and say nothing because it isn’t your section, or because you don’t want the attention turned on you, you are enabling it. I know that’s a difficult thing to hear. It’s still true.
  • After service matters as much as during it. The debrief is where you can be honest without the heat of the moment. If something went wrong, say so. If someone did well under pressure, say that too. Both deserve acknowledgement.

For the Younger Cooks Reading This

You will have bad services. You will make mistakes that cost the kitchen time and money and the goodwill of a table. You will be corrected in ways that feel sharp and uncomfortable. That is part of learning a demanding craft, and I’d be doing you a disservice if I pretended it wasn’t.

But if someone makes you feel worthless, not just corrected, not just challenged, but genuinely worthless, as a matter of routine, that is not the price of admission to a good kitchen. That is a badly run kitchen. And the belief that suffering makes you stronger, that the more you endure the better a chef you’ll become, is a myth that has cost this industry a generation of talent. Probably more.

Trust your instincts. If you feel unsafe, say so. If there’s a head chef or an HR function or an owner you can speak to, use them. If there isn’t, that tells you something important about where you’re working. Good kitchens, genuinely well-run kitchens, have answers to these questions. They are not perfect, none of them are, but they have answers.

The Standard You Set Is the Standard You Get

I’ve seen kitchens with ferocious standards and very low tolerance for sloppiness that were also, genuinely, decent places to work. The chefs there were direct, sometimes blunt, occasionally loud, but they were fair. They corrected the work. They explained what they meant. They remembered what it felt like to be new. The food was extraordinary, and the turnover was low, which is not a coincidence.

Running a tight kitchen and treating people with basic dignity are not in conflict. The idea that they are is the oldest excuse in the industry for behaviour that ought to have been left behind decades ago. A chef who can only get results by making people afraid has a limited repertoire, as a cook and as a person.

The kitchens I respect most are the ones where a commis can admit, mid-service, that something has gone wrong, and the response is: right, let’s fix it, what do you need. That’s not softness. That’s just how you get good food out of a brigade that trusts you enough to be honest with you.

Know the difference. Teach it. Hold to it. The food will be better for it, and so will everyone in the room.

Chef Ian McAndrew’s specialist eBooks and guides are available directly on ChefYesChef, including his technical titles and autobiography. If you want more practical, chef-led reading beyond this article, you’ll find the full collection here.

Chef Ian McAndrew works with chefs, businesses, and individuals on a wide range of culinary projects, from concept development to practical problem-solving.


If you’d like to talk through an idea or need informed guidance, you’re welcome to contact him.