Watch a rush go bad and you can usually trace it back to one person before it ever hits the ticket times. A manager tightens up. Voice gets sharper. Walk gets faster. Shoulders go up near the pass. Within two minutes, the whole kitchen has absorbed that energy and started making small mistakes they wouldn't make on a slow Tuesday.
This is not a motivational poster idea. It is a operational fact. Line cooks and servers are watching you constantly during a rush, even when it looks like they are too busy to notice. You are the barometer for how bad things actually are. If you look rattled, they assume it's a five-alarm fire even when it's just a normal Friday with two tables running late.
The fix is not "stay positive." It is a specific set of habits you can actually practice.
Control your pace before you control the room. If you are moving fast and talking fast, everyone downstream moves faster and gets sloppier. Slow your own walk. Slow your own voice by about twenty percent. It feels unnatural at first because your adrenaline is up too, but the floor calibrates to your pace, not your ticket count.
Give information, not emotion. "We're eighty-sixed on the ribeye, eight minutes out on table 12, servers grab bread for 14 and 15" is useful. A sigh, an eye roll, or "how did we get this far behind" is not useful, it just tells the team you're panicking and gives them nothing to act on. Every time you open your mouth during a rush, ask whether what you're about to say fixes anything or just broadcasts stress.
Designate one point person at the pass or the host stand who runs traffic while you float. Trying to expo, manage the door, and coach a new server through a mistake all at once is how a fifteen-minute wait becomes a forty-five-minute wait. Pick your point person before the rush, not during it, and make sure the whole team knows who has the ball.
Build the rush plan into your pre-shift, not your post-mortem. Most managers only talk about the rush after it goes sideways. Flip that. Before doors open on a Friday, spend ninety seconds on what today's specific pressure points are: a server out sick, a new cook on the line, a private party at 7. Naming the pressure points ahead of time means the team isn't discovering them in real time, which is when panic sets in.
Debrief the rush like you'd debrief a big shift, not just the disasters. Most teams only sit down after a bad night. Do a two-minute huddle after a strong, chaotic Friday too and ask what worked. Reinforcing the calm version of chaos is how you build a bench of shift leads who can run a rush without you standing over them.
Here's the part operators miss: this is trainable. Calm under pressure is not a personality trait some managers have and others don't. It is a set of specific behaviors, communication patterns, and pre-shift habits that get better with reps and get worse with neglect. If you've got a shift lead who tenses up every Friday at 7pm, that's not a character flaw, it's a training gap, and it's the same kind of gap that shows up in service recovery, in guest complaints, in how a team handles a walk-out. The operators who fix it treat it like any other skill: name the behavior, practice it, coach it, repeat it.
This is also why the standard you set on a calm Tuesday doesn't automatically show up on a slammed Friday unless you've actually built the habit into your shift leads, not just yourself. Wingman helps operators turn moments like this into daily training reps and accountability checks instead of one-off lectures after a bad night, so the lesson sticks with the whole leadership bench, not just the manager who happened to be on the floor that day.
If you want to see how Wingman helps you build calmer, more consistent shift leaders across every location, take a look at how the platform handles daily training and accountability.