From chef to leader: the skills nobody teaches you when you get the head chef role

Getting the head chef role is supposed to be the moment everything comes together. Years of early starts, late nights, learning the craft, working under pressure, proving yourself in someone else's kitchen. And then the role is yours.

What nobody tells you is that the job you just got is almost nothing like the job you have been preparing for.

Cooking is a technical skill. Leading a kitchen is a people skill. The two overlap in some places, but they are not the same thing and they do not develop through the same experiences. Becoming a brilliant chef does not automatically make you ready to lead a brigade, manage conflict, give feedback, hold accountability, or build the kind of culture where talented people actually want to stay.

This is not a criticism of chefs who struggle with the transition. It is an observation about the gap between what the industry rewards and what it actually requires.

What the transition actually involves

When you step into a head chef role, the nature of your responsibility changes completely.

You are no longer primarily accountable for what you produce. You are accountable for what your team produces. That sounds like a small shift but in practice it changes almost everything about how your days work.

You cannot be at every station. You cannot taste every dish before it goes out. You cannot personally guarantee every element of every service through your own hands. You have to trust other people, develop other people and, when things go wrong, work out what happened and how to stop it happening again without burning the relationship in the process.

None of that was on the training menu.

The feedback problem

Kitchens have a long tradition of blunt feedback. That tradition has its roots in high pressure environments where precision matters and there is no time for lengthy discussions mid-service. There is logic to it in that specific context.

The problem is that blunt, reactive feedback delivered under pressure rarely produces the behavioural change it is aiming for. What it usually produces is either compliance driven by fear, which is fragile, or resentment, which compounds over time.

The chefs who get this right have usually worked out, often through experience rather than training, that feedback works differently depending on when and how it is delivered. The correction in the middle of service is necessary and fine. The conversation about recurring patterns, about development, about where someone wants to go and what is holding them back, that is a different kind of conversation and it requires a different kind of skill.

Most head chefs are never given any support in developing that skill. They work it out themselves or they do not, and the culture of their kitchen reflects whichever way it went.

Running a team nobody wants to leave

Hospitality has a retention problem. The industry knows this. The response has typically focused on pay and conditions, which matter, but which are not the whole picture.

People leave managers more often than they leave jobs. This is well documented across industries, and kitchens are no exception. The chef who feels unsupported, overlooked or spoken to without basic respect will find another kitchen. The chef who feels invested in, challenged appropriately and treated like a person whose development matters will stay longer and work harder.

Building that kind of team starts with how you communicate. Whether you explain the why behind decisions or just issue them. Whether you notice when someone is struggling before it becomes a crisis. Whether the people working for you feel like they can raise something without it being used against them.

These are leadership behaviours. They can be learned. They are not personality traits that some people have and others do not.

The communication patterns that matter most

A few things come up consistently when I work with chefs who are developing their leadership practice.

The first is the briefing. Pre-service briefings in many kitchens are functional at best. A run through of covers, specials, any changes. Done in three minutes. The opportunity to set the tone for the whole service, to check in with the team, to identify anything that needs attention before it becomes a problem, is often missed entirely.

The second is the debrief. Post-service conversations are rare in a lot of kitchens. Everyone is tired, the work is done, people want to go home. But the ten minutes spent talking about what worked, what did not and what to do differently next time is often more valuable than any formal training session.

The third is one-to-one time. Regular individual conversations with the people you manage, not performance reviews, just ongoing conversations about how they are getting on and what they need, are probably the single highest-leverage thing a head chef can do to develop their team and reduce turnover. Most head chefs have never had a one-to-one with their own manager and so have never experienced what a well-run one feels like.

What experience alone does not teach you

There is a version of this that says experience is the best teacher and that given enough time, chefs who step into leadership roles will develop what they need.

Some do. But the cost of that learning, to the chefs themselves and to the teams on the receiving end of the process, is high. And time is the one resource that hospitality does not have in abundance.

The chefs who develop most quickly as leaders are usually the ones who get some structured support at the point of transition. Not because they are less capable than others, but because good leadership practice is not something most people develop intuitively. It requires deliberate attention and, usually, some outside perspective.

The craft takes years to develop. The leadership skills do not have to.