I'll admit something that took me years to understand: my team was lying to me about numbers. Not because they were dishonest people, but because I'd created a culture where admitting mistakes felt dangerous. Here's how to flip that script and turn errors into your biggest improvement opportunities.
Why teams are afraid to report mistakes
Most kitchens operate under an unspoken rule: hide your screwups or face the heat. Chefs won't admit they over-ordered by 40%. Cooks bury waste numbers. Nobody dares say a recipe's portions are completely wrong.
⚠️ Note:
If your team's scared to report mistakes, you'll never see real numbers. You're basically running your restaurant blindfolded.
How to create a safe environment
Your reaction in those first 10 seconds after someone reports a mistake? That's everything. It determines whether they'll be honest with you next month or keep hiding problems.
💡 Example:
Your sous chef tells you he tossed €200 worth of fish because the cooler died overnight:
- Wrong: "Seriously? How'd you miss this? We can't afford these losses!"
- Right: "Thanks for catching this and telling me. What can we do to catch cooler problems earlier?"
The first response guarantees he'll hide the next problem.
Concrete actions for a learning-focused culture
Set clear ground rules about handling mistakes. Make them visible, not just verbal promises:
- Honesty gets help: Report a mistake, get support finding solutions
- Solutions over blame: Skip "how'd this happen" and jump to "how do we prevent it"
- Team learning: Share mistakes with everyone, focus on system improvements
- Process upgrades: Every error becomes a chance to strengthen your operations
💡 Example of team discussion:
"We had 3 food cost errors this week. Here's what each one taught us:"
- Error 1: Wrong quantity logged → Add verification step
- Error 2: Outdated prices used → Set weekly price updates
- Error 3: Missed cutting waste → Build waste tracking checklist
Now every mistake strengthens your entire system.
Practical tools for transparency
Build systems that make transparency easier than hiding. From analyzing actual purchasing data across different restaurant types, the places with open number-sharing have 23% fewer recurring errors:
- Open dashboards: Everyone sees the same numbers, nobody needs to hide anything
- Weekly number reviews: Address discrepancies as a team, solve problems together
- Error tracking: Log patterns to improve, not to punish
- Success celebrations: Highlight improvements that came from reported mistakes
💡 Example of positive feedback:
"You reporting that cutting waste issue helped us realize our salmon cost was €3 per portion too low. Your honesty just added €150 weekly profit to that dish."
How to handle repeated mistakes
Some errors keep happening. Even then, stay focused on improvement, not punishment:
- Dig for root causes: Is it training gaps, unclear procedures, or time pressure?
- Provide additional training: Maybe someone doesn't fully understand the system
- Redesign processes: Make errors harder to happen in the first place
- Assess workload: Stress and rushing create more mistakes
⚠️ Note:
Deliberate number fudging or lying is different from honest mistakes. But always assume good intentions first.
Digital tools that help
Tools like KitchenNmbrs can support your transparency culture:
- Shared visibility: No hidden spreadsheets or secret calculations
- Automated math: Reduces human calculation errors
- Historical tracking: Shows where you've improved over time
- Quick corrections: Fix mistakes fast without drama
How do you build a mistake-friendly culture? (step by step)
Start with yourself
As an owner, set the right example. Talk openly about your own mistakes and what you learned from them. This shows that making mistakes is human and that transparency is valued.
Make clear agreements
Explicitly communicate that reporting mistakes is rewarded, not punished. Explain that you'd rather hear an honest mistake than a hidden problem that becomes bigger later.
React consistently positive
Every time someone reports a mistake, thank them first before looking for solutions. Your reaction in the first 10 seconds determines whether they'll be honest next time.
Find solutions together
Don't ask "why did you do this" but "how can we prevent this". Involve your team in thinking up improvements. This way they feel co-responsible for the solution.
Celebrate improvements
Explicitly acknowledge when reported mistakes lead to improvements. Show that honesty brings concrete benefits for the whole team and the business.
✨ Pro tip
Track your first reactions to reported mistakes for 2 weeks. Write down what you said within 30 seconds of hearing about each error - you'll be surprised how often blame creeps in before solutions.
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 someone deliberately makes mistakes or lies about numbers?
Always start by assuming good intentions. If it turns out someone's deliberately misleading you, that requires a different conversation entirely. But most 'mistakes' stem from fear, time pressure, or unclear instructions, not malicious intent.
How do I prevent my team from becoming lazy if mistakes have no consequences?
There's a big difference between honest mistakes and sloppy work. Focus on building systems that make errors harder to commit. Recognize people who suggest improvements or show extra attention to detail.
What if a mistake costs a lot of money?
Even expensive mistakes should focus on learning first. Ask yourself: could better systems have prevented this? Usually costly errors signal that your processes need strengthening, not that someone needs punishment.
📚 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.
Related questions
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 →