What It Actually Takes to Run a Section

 

People throw the word "chef" around like it just means someone who cooks well. It doesn't. Cooking well gets you in the door. Running a section is a completely different skill, and almost nobody explains it properly before you're standing there on your first solo shift wondering why you're drowning.

I want to break down what actually changes when you go from "cook who's good at their job" to "person responsible for a section," because the gap is bigger than most people expect.

Cooking and running a section are different jobs.

When you're a junior, your job is simple: execute the dish in front of you, well, on time. That's hard enough on its own. But running a section means you're not just cooking anymore — you're managing a system. You're tracking six, eight, ten dishes at different stages simultaneously, predicting when tickets are going to stack, and adjusting before it becomes a problem instead of after.

The cooking part is maybe 40% of the job at that point. The rest is timing, communication, and decision-making under pressure — skills nobody teaches you in culinary school, because they can't really be taught in a classroom. You learn them by getting buried a few times and figuring out what you should have done differently.

The tickets don't wait for you to catch up.

This is the part that breaks people early on. On a quiet section, you can cook in order — ticket one, ticket two, ticket three. On a section that's actually busy, that approach falls apart in about four minutes. You have to be thinking two, three, four tickets ahead. What's about to fire. What needs to rest. What can wait thirty seconds and what can't wait ten.

The skill isn't cooking faster. It's seeing further ahead than the ticket in front of you. That's the actual job.

Communication matters more than people think.

A section running well sounds a certain way — calls made clearly, times given honestly, problems flagged the second they happen instead of five minutes later when it's too late to fix. A section running badly sounds like silence, or like everyone shouting over each other because nobody said anything until it was already a crisis.

I've worked with cooks who were technically excellent and still struggled to run a section, because they wouldn't communicate. They'd rather struggle quietly than say "I'm behind" — and by the time it was obvious, it was too late for anyone to help. The best line cooks I've worked with weren't always the most talented with a knife. They were the ones who told the truth about where they were at, constantly, without ego.

You have to make decisions with incomplete information.

Nobody hands you a perfect plan. Two large tables fire at once. A dish comes back. Someone calls in sick and you're down a pair of hands. Running a section means making a call — right now, with what you've got — instead of freezing while you wait for more information that isn't coming.

Some of those calls will be wrong. That's fine. What matters is making a decision and adjusting, rather than hesitating and letting the whole section stall while you figure out the "right" answer. In a live service, a fast, reasonable decision beats a slow, perfect one almost every time.

Nobody arrives ready for this.

If you're a few months into running your first section and it feels like you're barely keeping your head above water — that's not a sign you're bad at this. That's what it's supposed to feel like at the start. The chefs who look calm running a busy section aren't calm because it's easy for them. They're calm because they've been buried enough times to know what buried actually feels like, and this isn't it.

Give it time. The panic fades before the difficulty does — you just get better at operating inside it.

— The Chef