The Restaurant Decides It Before The First Bad Night Arrives
The Restaurant Decides It Before The First Bad Night Arrives
I once hired a Sous Chef and watched them lose the team inside of eight weeks. They were still building toward the moment that would prove them. The kitchen had already decided.
It was a Friday night. Busy but not really busy. We’re only going to do 180 covers, and my new Sous Chef, Jacob, just in his third week, spent 11-minutes before service explaining to a Sauté Cook why his station was so messy. The Cook had worked that station for almost four years. He didn’t need the lecture. He needed those 11-minutes to fix it before tickets started dropping, and my Sous Chef wasted that time.
The Sous Chef thought he was doing the job. The line had already made up its mind about him by the time the first ticket hit the kitchen. He lasted another five weeks before he was gone, and he never understood what happened. He thought he was building toward the moment that would define him. The restaurant had already written him off on Wednesday.
Learn The Room Before You Decide To Run It
When you’re new to a position, spend your first two weeks figuring out the restaurant. What’s good! What’s bad! What’s mid!
Watch who gets called when the line’s drowning. Watch which Server the restaurant trusts when things turn ugly. Watch which part of the service starts slipping before anyone says it out loud. Watch. Take notes. Learn. Most new Managers are too busy introducing themselves to read it.
What you’re looking for are patterns. The same four tickets that hit the kitchen late every Saturday. The prep item that blows up the line every Thursday. The section that buries the same Server every weekend because nobody fixed the layout years ago. Those issues keep showing up because they’re built into how the place runs. Find one thing in your first week and fix it. The team will notice before you’ve said one word about what you’re planning.
Fix One Thing People Hate
You don’t need a grand plan in week one. You need one less problem.
Pick the thing everyone complains about, and nobody owns. The station that’s always behind. The guest issue that keeps cycling back. The prep item that burns the line two nights a week. Fix it and stay on it.
I had a Manager once who spent her first week redoing the server sidework list. Everyone hated the old one. Nobody had touched it in three years. She updated it, trained the team on it, and left a laminated copy at every station. Servers stopped asking the same questions at the start of every shift. It took her maybe four hours total. Three months later, people were still talking about it like she’d rebuilt the restaurant from scratch.
Know The Work Under Your Title
Run food. Bus tables. Work the line when it’s short. If you can’t bartend, pour wine, pull beers, and wash glassware. Jump in the dishpit when it’s falling apart. The first time you’re standing in the weeds next to a Line Cook at 7 pm on a Saturday, you’ll understand something about that station that no pre-service conversation was ever going to teach you.
In the first two weeks, the team’s figuring out whether you’re going to work to help them and the guests or only above it. They make that call fast. They rarely change their minds. I’ve seen Managers lose a kitchen before they ever had a bad night because they never got their hands dirty in week one.
Be Early, Be Ready, Be Boring About It
Shortly after you arrive, you should know what’s on the books, the weather, the staff, and where the night’s most likely to crack. If Friday’s going to be rough, say it before the first guest walks in. If you’re short on the line, adjust before service turns into damage control. Stop pretending you’ll figure it out when it gets there.
The team notices this before they can explain why it matters. Prepared people stand out because preparation is still rare. A lot of restaurants run on hope and adrenaline. The Manager who walks in with a real plan looks different right away.
Correct People Without Turning It Into A Thing
If you lead by barking, people do the minimum when you’re watching and work around you when you’re not.
When someone misses the mark, keep it simple. Say what happened. Say what should’ve happened. Say what needs to happen next time. Do it privately when you can. The whole team is watching the first few corrections, and they remember how you handled it a lot longer than whoever you were correcting does.
If you want clean stations, yours has to be the cleanest one on the line. If you want people to hold it together when the printer’s screaming and the floor’s going sideways, you can’t be the first one to unravel.
Own The Ugly Part
Some nights are bad. Guests are upset. Tickets run long. The team’s looking around to see who’ll take the hit. If you disappear into excuses at that moment, people remember it.
Own what’s yours. Fix what you can. Stop the bleeding first and figure out what caused it to bleed after the rush. I watched a Manager lose a team member over a single bad Saturday because he went invisible when it mattered. They needed to see him standing in the fire with them, and he wasn’t there. Whether they were going to follow him had been decided weeks earlier, and that night confirmed it.
Say What You Don’t Know
A lot of first-time Managers get caught by fake certainty.
They don’t know how this restaurant handles a situation, so they make something up. They haven’t figured out why the line keeps breaking, so they act as if they have always known what’s happening. Six days in and they’re already talking like they’ve been there for years. That’s how trust gets shredded before you even notice it’s gone.
“I don’t know yet, but I’ll find out.” Then find out, and come back with the answer. That sequence, done consistently, builds more credibility than a dozen confident-sounding guesses. Getting caught faking certainty is something teams seldom forget.
Translate Both Ways
A first-time Manager or Sous Chef lives in the middle. That’s the hard part.
For the Owners, for the Managers and Chefs you work with, you need to bring clean information without drama. For your team, you need to explain decisions without sounding like a shield for someone else’s bad call. Most people can only do one. The rare ones can do both without losing the truth in either direction, and those are the ones who get asked to stay when the restaurant goes through a hard stretch.
Keep Notes On The Shift
After a bad night, write down what broke, what held, and what you’d do differently next time. 30-seconds on your phone in the parking lot is enough. Those notes tell you what’s changing and what keeps looping back. They keep you honest about the early weeks, when people are still deciding what they think of you.
Pay attention to your openers and closers. That’s when the score is being kept.
I write about what happens in restaurants and what it takes to do the job better. Follow along for free.
#RestaurantManagement #KitchenCulture #FoodServiceLeadership #HospitalityIndustry #RestaurantOperations #Restaurant101



“Learn The Room Before You Decide To Run It”
‘nuff said
we've got a sous chef who said he had 11 years of experience. his first week revealed that was an absolute lie. he's still on the payroll.