I'll admit it: for years, I blamed my staff for repeated mistakes until I realized the real problem was my broken systems. Most kitchen issues stem from unclear procedures, poor communication, or inadequate tools - not human error. You can transform these frustrating conversations into productive system improvements.
Recognize system errors vs. human errors
Before confronting your team, first determine whether the problem lies with the system or individual performance. System errors are structural and repeat themselves with different team members - they're predictable patterns, not random mistakes.
💡 Example system errors:
- Recipes only exist in the chef's head
- Temperature measurements are forgotten because there's no reminder
- Orders get mixed up because there's no clear system
- Ingredients run out because nobody keeps track of inventory
Create a safe environment for honest feedback
Always start team discussions with the message that you're seeking improvements, not culprits. Make it clear that everyone's input on potential improvements is valued and necessary.
⚠️ Watch out:
Avoid phrases like "Who did this wrong?" Use instead: "How can we prevent this from happening again?"
Focus on processes, not people
Discuss concrete situations without naming names. Analyze together what went wrong in the process and how you can prevent it - based on real restaurant P&L data, most "people problems" actually trace back to unclear workflows.
💡 Example conversation:
"Last week, 3 dishes came back because they weren't prepared correctly. Let's examine our process:"
- Are the recipes accessible to everyone?
- Do we have clear quality controls?
- Is there enough time to work carefully?
Involve the team in finding solutions
Ask your team to actively think about improvements. They work with the systems daily and often spot problems first. Their input creates sustainable solutions that actually get used.
- "What would help you make this easier?"
- "What tools or procedures are we missing?"
- "How can we organize this better?"
Implement structural improvements
Ensure the agreed improvements actually get implemented. This might mean investing in better tools, clearer procedures, or additional training - but it's cheaper than constant turnover.
💡 Concrete improvements:
- Digital recipe database that everyone can access
- HACCP app for automatic reminders
- Clear workstation layout and labels
- Weekly check-ins about what's working/not working
Monitor and evaluate regularly
Schedule follow-up discussions to see if the new systems are working. Stay open to further adjustments if a solution doesn't work out - systems evolve, and so should your approach.
How do you conduct a constructive team discussion about system errors?
Analyze the problem beforehand
Gather concrete examples and determine if the problem is structural. Note when, how often and in which processes things go wrong. Prepare for the discussion with facts, not assumptions.
Start with the right mindset
Begin the discussion with: 'We're going to look at how we can improve our processes' instead of 'Too many things are going wrong'. Make it clear that everyone can contribute without fear of criticism.
Discuss concrete situations together
Walk through step by step what happened, without naming individuals. Ask the team where they think the process broke down and what would help them do it better.
Make concrete agreements
Decide together which improvements you'll implement. Make sure these are realistic and achievable. Schedule a date to evaluate how the new approach is working.
✨ Pro tip
Hold a 15-minute team huddle every Tuesday specifically focused on system improvements, not individual performance. This creates a regular outlet for process discussions and prevents small issues from becoming major problems.
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
How do I know if it's a system error or human error?
If the same problem occurs with different team members, it's likely a system error. Human errors are usually incidental and personal. Pay attention to patterns: does it happen regularly at the same times or with the same tasks?
What if my team reacts defensively during the discussion?
Repeat that you're seeking improvements, not culprits. Give a concrete example of a system improvement you've implemented before. Explicitly ask for their help: 'You know better than I do what's needed to do this right.'
How often should I have these kinds of discussions?
Schedule a short team meeting monthly where you ask what's working and what could be better. For acute problems: discuss immediately, but wait to make structural changes until you've analyzed the pattern.
What if the solution costs money I don't have?
Prioritize solutions that cost little but have high impact: better communication, clearer procedures, or rearranging workspaces. Calculate what errors cost you - often a small investment in a better system pays for itself quickly.
📚 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.
Give your team insight into the numbers
When your team understands what dishes cost, their behavior changes. KitchenNmbrs makes food cost visible to everyone in the kitchen. Start your free trial.
Start free trial →