Kitchen numbers trigger resistance because they're usually introduced as surveillance rather than support. Your team interprets data tracking as micromanagement or evidence you don't trust their skills. Numbers should create clarity about wins, identify where support is needed, and demonstrate how each person drives business success.
Why numbers create resistance
Most kitchen teams hate numbers because they're used the wrong way:
- As a stick to beat them with ("The food cost is too high!")
- To assign blame ("Who messed this up?")
- For control without explanation ("Just fill this in")
- Without showing what happens with the data
⚠️ Watch out:
Numbers without context feel like judgment. Your team assumes: "My work isn't trusted anymore."
Position numbers as a tool
Reframe the narrative. Data isn't about control—it's about empowerment:
- Insight: "Now we understand why yesterday felt chaotic"
- Recognition: "Your risotto is absolutely crushing it"
- Planning: "We'll prep extra for Friday's rush"
- Validation: "These dishes are serious profit drivers"
💡 Example:
Instead of: "The food cost on the steak is 38%, that's too high."
Try: "Our steak's popularity is incredible—let's brainstorm ways to boost its profitability even more. What's your take?"
Result: Collaboration replaces defensiveness.
Start with positive numbers
Lead with victories, not problems. Showcase what's working:
- "We served 15% more covers this week"
- "Your pasta station has the lowest waste"
- "Average check climbed to €28"
- "We're outperforming last year"
Once the team sees numbers deliver good news, resistance melts away.
💡 Example weekly briefing:
"This week we crushed 340 covers—12% jump from last week. The carbonara was our MVP with 85 portions sold. Waste stayed at just 3%, which is phenomenal work."
Then address issues: "Fish waste ticked up slightly. What ideas do you have to tighten that up?"
Make numbers relevant for each role
Different positions care about different metrics. After managing kitchen operations for nearly a decade, I've learned to tailor data to individual interests:
- Sous chef: Which dishes are selling best, where is help needed
- Commis: How their prep contributes to success
- Dishwasher: How clean equipment helps with quality
- Service: Which dishes they can recommend
Transparency about the why
Explain your tracking rationale. Mystery breeds mistrust:
💡 Temperature recording explanation:
"We log fridge temps daily not because I doubt your abilities, but because:"
- It protects our guests from food poisoning
- It prevents us from losing product to spoilage
- During inspections, we can prove our standards
"It's protection, not surveillance."
Use numbers for team development
Deploy data to elevate your team, not punish them:
- Spot training opportunities: "The new fish technique needs work—let's practice together"
- Amplify strengths: "Your sauce consistency is always perfect"
- Solve problems collectively: "How can we streamline mise-en-place?"
Celebrate small wins
Acknowledge improvements, however minor. Teams need recognition for their efforts:
💡 Example:
"Waste dropped from 8% to 6% this week. That saves us €180 weekly, or €9,360 annually."
"Your attention to detail made that happen. Excellent work."
Tools that help without threatening
Digital platforms can reduce friction because they:
- Provide objective analysis (no personal bias)
- Handle calculations automatically (less manual work)
- Highlight what's succeeding
- Show trends rather than isolated incidents
⚠️ Watch out:
Apps don't collect data automatically. Your team still logs temperatures and waste. The software just simplifies analysis and calculations.
Be patient with the shift
Trust building requires time. Don't expect instant acceptance:
- Week 1-2: Skepticism and resistance
- Week 3-4: Cautious acceptance
- Week 5-8: Getting used to it and first positive experiences
- Week 9+: The team starts bringing numbers themselves
Maintain your positive approach consistently, even when numbers disappoint.
How do you build trust in numbers? (step by step)
Start with one positive number per week
Choose one good number to share each week. For example: number of guests, best-selling dish, or low waste. Make it a ritual during your weekly briefing.
Always explain why you measure something
For every registration you ask for, explain the purpose. Not "because it has to be" but "because it helps us to..." Transparency pierces through distrust.
Celebrate small improvements big
If food cost drops 1% or waste is 2% less, make a celebration of it. Show that their effort is noticed and makes a financial difference.
Use numbers for team development
Instead of "This is going wrong", say "We can do better here". Use data to identify training needs, not to assign blame.
Make it relevant for each role
Show each employee how numbers help them personally. The sous chef wants to know which dishes are selling, the commis wants to see how their prep contributes to success.
✨ Pro tip
Share 3 positive metrics every Monday morning before discussing any improvement areas. Teams need to see numbers bring good news for at least 4 weeks before they'll trust the process.
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 refuses to keep numbers?
Start small with one simple measurement per day, like fridge temperature. Explain why it matters for food safety, not for control. Celebrate every small step.
How do I share bad numbers without damaging trust?
Always start with something positive, then the improvement point, and end with a question: "How can we make this better together?" Make it a challenge, not a reproach.
My chef thinks numbers are a waste of time, what now?
Show how numbers save time: less waste, better planning, no guessing on orders. Start with one number that directly makes their work easier.
How long does it take for my team to accept numbers?
Expect 6-8 weeks for real acceptance. The first month is mostly about breaking through resistance. Stay consistent and transparent about the why.
Can I keep numbers without involving my team?
That doesn't work. They know the kitchen best and need to fill in the data. Without their involvement, you get incomplete numbers and resistance persists.
What's the biggest mistake when introducing kitchen metrics?
Starting with problem areas instead of wins. Teams shut down when numbers only highlight failures. Always lead with positive data to build confidence in the system.
📚 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 →