The Reliable Cook Who Undermines the Shift
A grill cook with 8 years' tenure is the strongest technician on the line - fastest, cleanest, and the person others ask for help. But two newer cooks have privately told you they dread working his shifts: he corrects them loudly in front of others, takes over their station without asking, and once told a server "that's not my problem" in earshot of guests. Turnover among new hires on his shifts is higher. He has never been formally disciplined. He is also the only person who can run the grill on Friday and Saturday, and you have no trained backup. The GM wants him written up immediately; the chef wants to avoid conflict because "he's the best we have."
1. How do you reconcile the performance risk of losing him with the conduct problem, and what is your first step?
Read the worked answer
Frame it as two separate issues: his technical performance is real and valued; his conduct is a documented behavioral problem with a measurable cost (new-hire turnover, guest-facing rudeness). Letting conduct slide because of his skill is exactly what has let it persist.
First step - a private, specific conversation, not a write-up and not avoidance:
- State observed behaviors and their impact concretely (loud public correction, taking over stations, the server remark in guest earshot), without diagnosing his character.
- Make the standard explicit: corrections happen privately and respectfully; he coaches rather than seizes stations; guest-facing interactions are non-negotiable.
- Set a clear expectation and follow-up date, and document the conversation.
Why not the GM's immediate write-up: a write-up without a prior documented conversation is procedurally weak and escalates a fixable problem. Why not the chef's avoidance: it transfers the cost to new hires and guests and will eventually cost you the team.
Address the dependency in parallel: his being the only Friday/Saturday grill operator is a business risk independent of his conduct - start cross-training a backup now so the decision isn't hostage to his schedule.
2. The behavior improves for three weeks, then recurs. What now, and how do you protect the newer cooks in the meantime?
Read the worked answer
Escalate on the documented path: a second conversation referencing the prior one, a formal written warning tied to the specific recurring behaviors, and clear consequences. The recurrence after a documented conversation and improvement period is what justifies formal action - the record now supports it.
Protect the newer cooks now, not later:
- Tell them explicitly what standard of treatment to expect and how to raise concerns, and confirm you're acting on it - otherwise they conclude complaints go nowhere and leave.
- Separate the coaching relationship where possible: assign their development to another strong cook so they aren't dependent on him for help.
- Watch for retaliation; a cook who corrects loudly in public may react to being reported.
Reduce the dependency that gives him leverage: accelerate backup grill training so scheduling no longer hinges on one person. This is the real fix - it converts an "untouchable" employee into a normal one.
Decision rule: if conduct recurs after a formal warning, proceed to the next step in your policy regardless of his skill. Retaining a high performer who drives out new hires is often a net loss once replacement and training costs are counted.