Built from 28 years in restaurant operations. What actually works in the first 90 seconds — and what makes it worse.
Crew conflict in a restaurant doesn't wait for a convenient moment. It happens during a lunch rush, in front of other employees, when you're already managing four other things. Most managers freeze — not because they don't know what to do eventually, but because the first 90 seconds are the hardest part and nobody ever taught them how to handle those.
This guide is built from 28 years of restaurant operations experience. What actually works. What makes it worse. And what you can say in the moment before the situation sets in the wrong direction.
Unresolved crew conflict doesn't stay contained. It spreads through the team as behavioral data — other employees watch how you respond and draw conclusions about what's acceptable. A crew member who publicly defies you and walks away without consequence has just taught everyone else in the room that defiance is low-risk.
Talking back, dismissive responses, eye-rolling, or direct defiance in front of other employees or customers. This is the highest-priority conflict type because the audience dimension makes it an authority challenge, not just an attitude problem.
The employee who doesn't push back directly but consistently finds ways to avoid tasks, slow-walks requests, or does the minimum. This is harder to address because there's nothing dramatic to point to — but the pattern is just as damaging over time.
Two employees who can't work together, argue on the floor, or create a hostile environment for the team. Your job is not to pick a side — it is to restore the working environment and hold both parties to behavioral standards.
The most expensive mistake restaurant managers make in conflict is responding emotionally in a public setting. Matching the energy of a disrespectful employee in front of the team doesn't restore authority — it transfers the authority problem to you.
Your goal in the first 90 seconds is to neutralize the public dimension without escalating it. One calm, direct sentence — then move the conversation private.
"We'll talk about this after the rush. Right now, I need you on the prep station."
This does two things: it signals that the behavior is not being ignored, and it removes the audience from the equation without creating a scene.
This is where the real reset happens. Pull them aside — not in the walk-in, not in a hallway where others can overhear. Somewhere private. Keep it under ten minutes.
Open with what happened, not with how you feel about it:
"What happened earlier — talking back to me in front of the team — that can't happen. I'm not here to go back and forth about it. I need you to understand that's not how we handle things here. If you have an issue with something I'm doing, you come to me directly and privately. Are we good?"
Even if the conversation goes well, document the incident the same day. Date, what happened, what was said in the corrective conversation, and the employee's response. If it happens again, you have a pattern. Without documentation, every incident is the first incident.
When you describe a conflict situation to Helios, the Conflict Translator module activates automatically. It doesn't ask you which module to use — it reads the situation and responds.
A typical Conflict Translator response gives you: what the conflict dynamics actually are, an assessment of the damage to your authority, specific language for your next conversation, and a closing question that helps you understand the root cause before you walk in.
It's available the moment you need it — not after you've already handled it wrong.
Describe what happened. The Conflict Translator activates automatically and gives you specific language for your next move.
Start Free — 14 Days No charge until day 15. Cancel anytime.