Here's something most restaurant owners won't admit: their weekly number reviews feel more like a courtroom than a team meeting. Staff brace themselves for criticism, chefs get defensive before you even speak. But it doesn't have to be this way.
Start with appreciation, not problems
Begin every number discussion with what's working. Which dishes are killing it? What made you proud this week? Only after celebrating wins should you tackle the challenges. This simple shift prevents your team from immediately going into defense mode.
💡 Example:
"Our pasta carbonara is crushing it - 28% food cost and customers can't get enough. You've nailed that dish. Now, I'm curious about the steak sitting at 38% food cost. How do we get it performing like the pasta?"
Make it a puzzle you solve together
Present numbers as mysteries to crack, not verdicts to deliver. "Food cost jumped to 36% this week. What's your take on that?" Let them analyze first. You'll be surprised how often they already know what went wrong.
- Ask for their read on the situation before sharing yours
- Acknowledge smart observations from your team
- Hunt for solutions, not someone to blame
- Say "we" way more than "you"
Explain why numbers matter
Most kitchen staff don't connect food costs to their daily reality. Break it down: "Better food cost control means we can afford that new convection oven you've been wanting and maybe bump up wages next quarter."
💡 Example:
"Dropping our food cost from 34% to 29% frees up €1,800 monthly. That could mean:
- Premium ingredients for specials
- That salamander upgrade we discussed
- Performance bonuses for the team
Focus on behavior, not people
Talk about what happened, not who's responsible. "Protein waste spiked this week" hits differently than "You're wasting too much meat." One of the most common blind spots in kitchen management is making discussions feel personal when they should be systematic.
⚠️ Watch out:
Don't call out individuals during group meetings. Save specific feedback for private conversations, not public forums.
Make agreements and check results
Every discussion should end with clear next steps. What's changing? Who's doing what? And most importantly: how will you celebrate when things improve?
- Specific actions assigned to individuals or stations
- Follow-up date to review progress
- Recognition plan for hitting targets
- Flexibility to adjust if strategies aren't working
Use visual aids
Raw percentages mean nothing to most people. Show them what 34% food cost looks like in actual dollars lost per service. Make waste tangible by showing exactly how much product hit the trash.
💡 Example:
"We tossed €165 worth of produce this week. That's like comping an entire table every single day. Cut that waste in half and we're looking at a team dinner next month."
How do you organize a positive number discussion? (step by step)
Prepare the numbers clearly
Make sure you understand the key numbers before bringing the team in. Food cost, waste, and sales figures per dish. Prepare 2-3 concrete examples everyone recognizes.
Start with positive points
Always begin with what's going well. Which dishes are performing strongly? What is the team proud of? Create a positive atmosphere before discussing improvement areas.
Present challenges as puzzles
Ask questions instead of drawing conclusions. "What do you think happened with food cost this week?" Let the team think along and come up with solutions.
Make concrete agreements
End with clear actions and a date to check results. Make sure everyone knows what's expected of them and when you'll discuss progress.
✨ Pro tip
Schedule number reviews for the same time each week - Tuesday at 2 PM works well since Monday's too chaotic and Friday everyone's mentally checked out. Consistency removes the surprise factor that makes these conversations feel punitive.
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 often should I review numbers with my kitchen team?
Weekly quick check-ins work best - maybe 12 minutes max. Then do deeper monthly reviews for 30-40 minutes. More frequent feels like surveillance, less frequent and small problems become major headaches.
What if my sous chef shuts down during number discussions?
Start by highlighting something they're doing right before diving into issues. Ask what they think about the numbers first, then share your perspective. Make it feel collaborative, not interrogational.
Should I discuss individual performance in team meetings?
Absolutely not. Team meetings are for collective goals and system improvements only. Individual feedback always happens privately, never in front of peers.
How do I make food cost percentages meaningful to line cooks?
Translate everything into real money and real consequences. Show them how waste translates to lost equipment upgrades or missed bonus opportunities. Make it personal to their daily work experience.
What if my team claims they don't understand the financial side?
Use concrete examples instead of abstract numbers. "€140 in waste equals throwing away two cases of premium steaks" resonates more than percentages ever will.
How do I handle pushback when staff blame suppliers or customers?
Acknowledge their concerns first, then redirect to what you can control. "You're right, that delivery was late. Now, how do we adjust our prep schedule to handle that better next time?"
What's the best way to celebrate when numbers improve?
Make the celebration as visible as the original problem discussion. Announce improvements publicly, connect them to the team's specific efforts, and deliver on any rewards you promised. Recognition works better than cash sometimes.
📚 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 →