Chef Retention Strategies That Actually Work


TL;DR: Sous chef promotion advice rarely covers this: the head chef role is a management job that involves cooking, not the other way round. If you want the title more than the work that comes with it, that is worth knowing before you accept.
Most sous chefs who say yes to a head chef role have not actually asked themselves whether they want the job. They want the title. And that distinction matters more than any amount of sous chef promotion advice anyone can give you.
I have watched talented cooks take the step up and completely unravel. Not because they lacked skill. They could cook rings around half the people I have worked with. But they did not want to spend their days managing a rota, having the same conversation with a food supplier for the fourth time that week, and lying awake at two in the morning because the fish order was short and there is a private dinner for thirty on Saturday. They wanted the white jacket with the name on it. Which is understandable, honestly. It is a very nice jacket.
The problem is that the jacket comes with everything else attached to it.
Here is what most chef career progression conversations skip entirely: the head chef role is a management job that happens to involve cooking, not a cooking job that happens to involve management. The ratio shifts the moment you walk through that door with a new title. Suddenly you are responsible for food cost, labour cost, consistency across every cover, allergen compliance, the mental health of a twenty-two-year-old commis who is not coping, and whether the new pastry section works within the budget. You are also still expected to run a clean, precise, creative kitchen.
Nobody tells you that the cooking part, the part you presumably love, gets smaller. Not because you have lost anything, but because the job genuinely requires other things from you now. If that sounds like something you would find satisfying, excellent. If it sounds like a list of things you actively dislike, that is worth sitting with for a while before you say yes.
When I was a sous chef, I thought the main thing holding me back was opportunity. I was wrong. The main thing I had not reckoned with was whether I wanted the full weight of it. The cooking I was absolutely certain about. The rest of it I had not properly imagined. I thought leadership would feel like running the pass with a bit more authority. It does not. It feels like being responsible for everything that goes wrong, including things that were not your fault and were never going to be your fault, while also being expected to have a clear creative direction and keep the brigade motivated through a heatwave in August when two people are off sick.
So before you say yes to anything, answer this honestly: do you want to lead people, or do you want to cook? Both are entirely valid answers. But they point in different directions.
The chef job title vs responsibility gap is enormous, and the industry does not talk about it enough. A head chef title carries weight socially. It reads well. Your parents finally understand what you do for a living. But the responsibility attached to that title is not glamorous. It is granular, repetitive, and often invisible. Nobody sees you doing the stock rotation audit. Nobody applauds when you sort out the rota without anyone noticing there was ever a problem.
What people do see is the food. And if you have a strong sous chef running sections brilliantly, some of what they see may not even be directly yours. That is fine, that is how good kitchens work, but it requires a particular kind of ego management that not everyone has or wants to develop.
Ask yourself the following. Be blunt with yourself, which is harder than it sounds when ambition is involved.
There are no right answers to these in the sense that there is no formula. But if you answered honestly and most of those made you feel slightly tired just reading them, that is information.
When you are moving from sous chef to head chef, the technical skills largely transfer. You already know how to cook. What does not transfer automatically is the shift in how the team relates to you. As a sous chef, you are somewhere between peer and authority. As a head chef, that ambiguity disappears, and some cooks find that distance lonely in ways they did not anticipate. The banter changes. The dynamic changes. You are no longer entirely one of them, and that takes some getting used to.
You also inherit the kitchen’s existing problems. Whatever the previous head chef left behind in terms of culture, habits, or supplier relationships, that is now yours to either maintain or fix. Walking into a promotion assumes a clean slate. It rarely is one.
This is the part that trips up most people. Culinary leadership skills are learnable, but they are not the same as being brilliant at your station. You can be the finest fish cook in the county and still be a mediocre leader. The two abilities are related in roughly the same way that being good at eating is related to being good at cooking. There is some overlap, but not nearly as much as you would think.
Leadership in a kitchen means clear communication under pressure, consistent standards applied fairly across the whole team, and the ability to develop people rather than just use them. If you have been a sous chef who hoards technique because sharing it might make you dispensable, that habit will actively damage you as a head chef. You need your team to be good. Their success is your success.
Chef career progression does not have to mean moving upward into management. That is one path. But there are sous chefs who are genuinely in the right role. They are exceptional at what they do, they thrive in the second position, they have a quality of life that suits them, and they have no particular desire to take on the full weight of running a kitchen. There is no shame in that. There is enormous skill in that.
The problem is that the industry still treats staying as a sous chef as somehow not quite making it. That is a structural nonsense. A brilliant sous chef who stays in the role and develops other cooks is worth considerably more to a kitchen than a mediocre head chef who took the promotion because it was offered and has been vaguely overwhelmed ever since.
If you do want the head chef role, and you want it for the right reasons, including the responsibility and not just the recognition, then take it and commit to learning the bits of it that do not come naturally. Ask questions. Find someone who has done it well and is willing to be honest about how they did it. Get comfortable with the administrative side before it buries you.
Readiness is less about technical ability and more about appetite for responsibility. If you are already making decisions that affect the whole kitchen, handling team issues, contributing to menu direction, and finding that satisfying rather than draining, you are probably ready. If you are doing those things and counting the minutes until you can get back to your station, the role may not suit you.
Sometimes, yes. The experience of running a kitchen, even a smaller or simpler one, teaches you things about leadership and operations that no amount of watching a head chef will give you. The risk is that you pick up habits and patterns from a lower-pressure environment that do not transfer well when the stakes go up. Go in with your eyes open about what you want to take away from the experience, not just what the role offers on paper.
Then you deal with it honestly rather than staying in a role you are miserable in and taking the team down with you. It is not a failure to recognise that a role does not suit you. It is considerably more damaging to grind through it badly for two years because you do not want to admit you made the wrong call. Good kitchens need people in the right roles, not people clinging to titles.
The title will not make the job feel different to what the job actually is. If you want to run a kitchen because you want to shape a team, build something, and take genuine ownership of a creative direction, say yes. If you want it because it sounds better at dinner parties, you might want to think again. The kitchen will find you out either way, and it will do so very quickly.
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