I used to think my "if it ain't broke, don't fix it" team was efficient. Then our walk-in cooler died on a Friday night with no backup plan. We lost €1,800 in spoiled inventory and angry customers.
Why teams avoid scenarios
Most kitchen crews live in crisis mode. There's always something screaming for attention: late deliveries, broken equipment, surprise rushes. Planning for "what if" scenarios feels pointless when you're drowning in "what now" problems.
💡 Example:
Your sous chef says: "Why plan for the oven breaking? It runs perfectly."
Three weeks later it fails during Saturday dinner service. No repair contacts saved. No workaround planned. Lost revenue: €2,200.
Result: Eight minutes of scenario planning would've saved €2,200 and countless headaches.
Start with their war stories
Skip the hypotheticals. Your team has battle scars from real disasters. Ask: "What disaster hit us hardest last quarter?" Then follow up with "How do we avoid that mess again?"
- Delivery truck broke down: Which backup supplier can we call?
- Ran out of house special: What substitute keeps customers happy?
- Key cook called in sick: Who steps up and handles their stations?
- Dishwasher quit mid-shift: What's our emergency protocol?
This doesn't feel like tedious planning. It feels like getting revenge on problems that already burned you.
Keep sessions laser-focused
Kitchen staff won't sit through hour-long brainstorming marathons. Limit each scenario discussion to 8-10 minutes max. Cover just three essentials:
- What's our immediate response if X happens?
- Who's in charge of executing the plan?
- What resources do we need ready (contacts, backup equipment)?
⚠️ Note:
Don't create endless scenario lists. Target the 4-6 situations most likely to wreck your service and cause serious losses.
Tap their street smarts
Your crew already knows where disasters lurk. They've survived equipment failures, supply shortages, and staffing nightmares. Don't ask "What might go wrong?" Ask "What's gone wrong before that we handled badly?"
💡 Example conversation:
You: "What was your biggest nightmare shift last year?"
Line cook: "Gas burners died during dinner rush. Complete chaos."
You: "What would've saved us?"
Line cook: "Maybe use the salamander more. Or have that portable burner ready."
Result: You've got a solid backup plan without anyone feeling micromanaged.
This mistake costs the average restaurant EUR 200-400 per month - teams that only react to crises instead of preventing them burn through extra labor, waste inventory, and lose customers who won't return after bad experiences.
Document it (but keep it dead simple)
Great scenario planning is worthless if you forget it mid-crisis. But skip the complicated manuals. A basic list on your phone or tools like KitchenNmbrs works perfectly:
- Deep fryer fails: Switch to cast iron pans, call Mario's Repair (06-87654321)
- Oven dies: Max out the grill, emergency pizza order from Tony's (020-9876543)
- Salmon delivery missing: Push the cod special, call backup supplier ASAP
Weave it into existing routines
Address one scenario weekly during your regular team briefing. Don't schedule separate meetings. Just add: "Remember when X went sideways last month? Let's nail down our response for next time."
💡 Practical tip:
Match scenarios to seasonal patterns:
- Winter: What if heating system fails during blizzard?
- Summer: What if patio gets slammed during heatwave?
- Holiday season: What if suppliers can't deliver on time?
This approach feels logical, not like busywork.
Celebrate proactive thinking
Notice when someone prevents a disaster through forward thinking. "Smart move ordering extra ribeye - we would've been screwed without it." Your team learns that scenario planning pays real dividends.
Start ridiculously small
Begin with one scenario monthly. Once your crew sees the results (less panic, smoother service), they'll ask for more planning sessions. Let demand grow naturally.
How do you get your team on board with scenario planning?
Start with their experiences
Ask what went wrong last month instead of coming up with hypothetical scenarios. Use their frustrations as a starting point for solutions.
Keep it short and concrete
Discuss one scenario in 10 minutes. Focus on three questions: what do we do, who takes the lead, what do we need?
Document it simply
Create a short list of actions per scenario. No long documents, just practical step-by-step plans everyone can understand.
Make it routine
Discuss one scenario per week during briefing. Link it to seasons or recent events so it feels natural.
Reward forward thinking
Acknowledge when someone prevents a problem through planning. This teaches your team that scenario planning is valuable, not a waste of time.
✨ Pro tip
Schedule scenario discussions for Tuesday mornings at 10 AM when your team is alert and the kitchen is calm. Timing this conversation right means the difference between eye-rolls and genuine engagement.
Calculate this yourself?
In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.
Was this article helpful?
Frequently asked questions
What if my team claims they're too busy for scenario planning?
Begin with 5-minute discussions tied to disasters they've already lived through. Prove that 5 minutes of planning prevents hours of chaos and stress.
How many scenarios should we actually prepare for?
Focus on 4-6 scenarios with the highest probability and biggest potential damage. Better to have solid plans for likely problems than weak plans for everything imaginable.
What happens when we face a scenario we never planned for?
That's completely normal and expected. Debrief afterward to figure out your response plan for next time. You'll gradually build a comprehensive scenario library this way.
How often should we update our scenario plans?
Review your scenarios every three months to keep them current. Phone numbers change, suppliers switch, and new equipment needs different emergency protocols.
📚 Sources consulted
- EU Verordening 852/2004 — Levensmiddelenhygiëne (2004) — Official source
- EU Verordening 853/2004 — Hygiënevoorschriften voor levensmiddelen van dierlijke oorsprong (2004) — Official source
- EU Verordening 1169/2011 — Voedselinformatie aan consumenten (2011) — Official source
- NVWA — Hygiënecode voor de horeca (2024) — Official source
- NVWA — Allergenen in voedsel (2024) — Official source
- Codex Alimentarius — International Food Standards (2024) — Official source
- FSA — Safer food, better business (HACCP) (2024) — Official source
- BVL — Lebensmittelhygiene (HACCP) (2024) — Official source
- Warenwetbesluit Bereiding en behandeling van levensmiddelen (2024) — Official source
- WHO — Foodborne diseases estimates (2024) — Official source
Food Standards Agency (FSA) — https://www.food.gov.uk
The HACCP standards shown in this application are for informational purposes only. KitchenNmbrs does not guarantee that displayed values are current or complete. Always consult the FSA or your local authority for the latest regulations.
Written by
Jeffrey Smit
Founder & CEO of KitchenNmbrs
Jeffrey Smit built KitchenNmbrs from 8 years of hands-on experience as kitchen manager at 1NUL8 Group in Rotterdam. His mission: give every restaurant owner control over food cost.
Make better decisions with real numbers
Should you change your menu? Raise prices? Test a new concept? KitchenNmbrs simulates scenarios with your own data. Try it free for 14 days.
Start free trial →