Chef Burnout Prevention: Spot It Before They Quit


TL;DR: Kitchen aggression is a management failure, not a sign of high standards. It persists because it went unchallenged for decades. Kitchens that replace it with clear leadership retain better staff and produce more consistent food.
Kitchen aggression is one of the most persistent and least examined problems in the professional cooking world, and most of us who came up through serious kitchens have either witnessed it, received it, or, if we’re being honest, occasionally handed it out. That last part is uncomfortable to admit. Which is probably why it doesn’t get admitted nearly enough.
I started my first kitchen job at sixteen, washing up in a hotel in the north of England where the head chef communicated primarily through volume and the occasional thrown ladle. Nobody thought this was odd. It was just how kitchens worked. You kept your head down, you got on with it, and if someone screamed at you for plating a dish incorrectly, you assumed the fault was yours. The idea that the screaming itself might be the problem didn’t really occur to anyone.
Let’s be clear about what we mean. Kitchen aggression isn’t someone raising their voice once during a busy Saturday service because three tables just came in at once. That’s adrenaline. That’s pressure doing what pressure does. Kitchen aggression is the sustained, habitual use of intimidation, humiliation, shouting, and in some cases physical menace, as a management style. It’s the chef who screams not because service is collapsing but because screaming is their default mode. It’s the culture where a new cook expects to be belittled as a rite of passage and where anyone who objects is told they can’t handle a real kitchen.
There’s a specific vocabulary around it that I’ve always found telling. People call it ‘old school’. They say it ‘toughens you up’. They talk about the ‘heat of the kitchen’ as if proximity to a stove justifies cruelty. It doesn’t. What the vocabulary actually does is protect the people doing the shouting from having to examine themselves.
Professional kitchens have always run on hierarchy. There’s a reason for that. A brigade system works because everyone knows their job, their station, and who gives the instruction at the pass. Clear hierarchy produces clean, consistent food. But hierarchy is not the same as tyranny, and a lot of people have spent decades confusing the two.
Part of why kitchen aggression persists is simple replication. Chefs manage the way they were managed. If your formative years in the industry involved being sworn at for a slightly underdressed salad, there’s a genuine risk that you file this away as ‘how kitchens work’ and reproduce it when you get your own section. It takes a degree of self-awareness, and frankly a degree of courage, to stop that cycle. Easier to tell yourself it never did you any harm.
There’s also the mythology of the tortured genius. Television didn’t create this, but it certainly amplified it. The idea that culinary brilliance and emotional volatility are somehow linked is, in my experience, almost entirely false. The most technically gifted chefs I have worked with have also been the most controlled, the most precise, the most calm under genuine pressure. Screaming is not a symptom of passion. It’s usually a symptom of poor stress management and, underneath that, insecurity about authority.
This is the part nobody much wants to hear. When a chef routinely humiliates their team, what they’re almost always communicating is that they lack the tools to manage people any other way. Shouting feels like control. It produces an immediate visible response, people move faster, they flinch, they comply. But it’s borrowed time. The compliance is fear-based, which means it disappears the moment the fear goes away, and it produces kitchens full of people who won’t tell you when something’s wrong because they’ve learned that bringing bad news attracts punishment.
I worked briefly under a chef who was genuinely explosive. Brilliant cook, catastrophic manager. His kitchen produced technically correct food and a turnover rate that would have embarrassed a fast food franchise. Every three months, new commis, new CDP, same screaming. He interpreted this as evidence that modern cooks couldn’t take it. What it actually demonstrated was that modern cooks had options, which they did, and they used them. He retired bitter and baffled. I think about him more than I should.
Toxic kitchen culture has real consequences for chef mental health, and the industry has been slow to acknowledge this. Long hours, physical exhaustion, poor pay at the lower levels, and an environment where asking for help is coded as weakness: these are conditions that produce burnout, anxiety, and worse. Add sustained aggression from a senior chef and you have something genuinely harmful.
The hospitality industry has higher rates of substance misuse and mental health difficulties than most other sectors. That’s not a coincidence. It’s a direct outcome of a working culture that has historically treated people as disposable and treated distress as softness. When we normalise aggression in kitchens, we’re not toughening people up. We’re grinding them down and then acting surprised when they leave, or worse, when they don’t leave but stop caring about the food.
I’ve had cooks come to me, mid-service, quietly, asking if they were doing alright, not because the dish was wrong but because they’d been told so many times in other kitchens that everything they did was wrong. That takes a while to undo. It’s not dramatic or sudden. You just gradually, over weeks, notice them standing a little straighter and asking better questions.
This is the part where I expect some pushback, but I’ll say it plainly: the calmest kitchens I have worked in have also been the most consistent ones. Not silent kitchens, not kitchens without pressure or intensity, but kitchens where the standard is enforced through expectation and example rather than intimidation.
When people aren’t frightened, they communicate. A cook who isn’t scared of the chef will tell you when the stock tastes off, when the mise en place is running low, when something on the pass doesn’t look right. That information is operationally critical. A frightened cook keeps quiet and hopes for the best, which in kitchen terms means you discover problems at the moment they become disasters.
Retention also matters more than I think most kitchen owners properly account for. Every time you lose a trained cook, you lose weeks of service knowledge. You lose the person who knows how you like the stock reduced, who runs the section without being told, who already knows the menu inside out. Replacing them costs money, time, and consistency. A kitchen where people want to stay is, practically speaking, a kitchen that produces better food, because the people making it know what they’re doing.
Changing a kitchen culture is not a matter of putting a new policy on the noticeboard. It starts with whoever is running the kitchen deciding, genuinely, that they are responsible for the environment they create. Not responsible for the food alone, but responsible for the people producing it.
That means giving clear feedback instead of delivering verdicts. It means explaining why something was wrong, not just that it was wrong. It means noticing when someone is struggling before they collapse, and treating that as useful information rather than weakness to be punished. None of this is complicated. Most of it is just ordinary human decency applied to a professional context.
It also means being honest about the fact that a lot of senior kitchen figures carry habits that aren’t serving anyone, including themselves. That’s a harder conversation, and it’s one the industry is still learning to have without either moralising or minimising.
The kitchens that have moved in this direction aren’t soft. They’re precise, demanding, and serious about the food. They’re also places where people build careers rather than just survive them. Which, if you care about cooking as a craft and not just a performance of toughness, is rather the point.
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.
Essential cookies required for the site to function. Cannot be disabled.
Cookies that help us understand how visitors use the site.
Cookies used to deliver relevant advertisements.
Privacy Policy Terms of Service