Picture this: your team meeting starts with groans as you pull out the weekly reports. Everyone's thinking about prep work while you're talking percentages. Numbers don't have to kill the energy in your restaurant meetings.
Why numbers are often boring in meetings
Most team meetings about numbers fail because they're too abstract. Your chef hears '32% food cost' but has no idea what that means for his daily work. Your server hears 'average check €24.50' but doesn't understand how they can influence that.
The problem: numbers without context are useless.
Make numbers personal and recognizable
Turn abstract percentages into concrete situations everyone recognizes:
💡 Example:
Instead of: 'Our food cost has risen to 35%'
Say: 'Last week we spent €240 too much on ingredients. That's like we gave away 12 steaks for free.'
Immediately recognizable for everyone.
- From percentage to euros: '3% more food cost' becomes '€180 per week extra costs'
- From averages to portions: 'Average check €22' becomes 'Every guest spends €22, that's 2 main courses'
- From monthly figures to daily impact: '€2,000 loss' becomes '€67 per day, that's 3 extra covers'
The 5-minute number-check routine
Start every meeting with a quick round of 3 numbers everyone understands:
💡 Example weekly meeting:
- Revenue: 'This week €8,400, last week €7,800. That's 25 extra covers.'
- Most popular dish: 'Salmon sold 47 times, pasta 31 times. Salmon wins.'
- Waste: 'Yesterday 2 portions of carbonara thrown away. Why?'
Total time: 3 minutes. Everyone knows where we stand.
Gamification: make it a game
People love competition and achieving goals. Use that energy:
- Daily challenge: 'Can we stay under 30% food cost today?'
- Weekly score: Team gets points for low waste, high average check
- Monthly winner: Who contributes most to profitability?
⚠️ Watch out:
Don't make it too competitive. It's about team performance, not individual blame.
Visual tools that work
Numbers on paper are boring. Make them visual:
- Whiteboard with daily standings: Revenue, covers, top 3 dishes
- Color-coding system: Green = good, yellow = watch out, red = action needed
- Chart on tablet: Show trend from past week
💡 Example visual dashboard:
Monday through Friday on whiteboard:
- Mon: 67 covers (🟢), food cost 29% (🟢)
- Tue: 71 covers (🟢), food cost 34% (🟡)
- Wed: 45 covers (🟡), food cost 31% (🟢)
Everyone sees the trend immediately.
Involve everyone in the solution
Numbers are only interesting if people can do something with them. Don't just ask 'what went wrong?' but also 'how do we make it better?' This mistake costs the average restaurant EUR 200-400 per month - talking about problems without creating solutions.
- Chef: 'Food cost is high, which ingredients have become more expensive?'
- Server: 'Average check is low, which side dishes can we promote more?'
- Everyone: 'We throw away a lot, how can we estimate portions better?'
Use a system everyone understands
Sharing Excel sheets in meetings doesn't work. Nobody understands what they're looking at. Tools like KitchenNmbrs show numbers in understandable dashboards you can share live during meetings.
💡 Example dashboard in meeting:
Show on tablet:
- Top 5 dishes this week with food cost per portion
- Which ingredients have become more expensive
- Comparison with last week
No Excel, no complicated calculations.
Start small, build up
Start with 1 number per week that everyone finds interesting. Slowly build up to more data. Too much at once overwhelms your team and kills engagement.
How do you make numbers interesting in team meetings?
Choose 3 relevant numbers
Pick yesterday's revenue, best-selling dish, and one cost item (like waste). More than 3 numbers at once is too much.
Translate into recognizable situations
Don't say '32% food cost' but 'we spent €150 too much on ingredients, that's 6 free main courses'. Everyone understands what 6 free dishes means.
Ask for input from the team
Don't just show numbers but ask 'why do you think this is?' and 'how can we improve this?'. Make it a conversation, not a monologue.
✨ Pro tip
Dedicate exactly 90 seconds each week to celebrate one number that improved. 'Our carbonara portions went from 180g average to 165g - that saved us €47 this week.' Teams remember wins better than 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 often should I discuss numbers with my team?
Start with 1x per week, 5 minutes at the beginning of your team meeting. As the team gets used to it, you can do daily check-ins of 2 minutes.
What if my team isn't interested in numbers?
Make it personal and show impact. High food cost means less money for equipment upgrades or staff bonuses. Connect the dots between their daily actions and restaurant success.
Which numbers are most important to share?
Start with yesterday's revenue vs. last week, number of covers, and the most popular dish. Everyone understands these numbers and they're directly relevant to daily operations.
How do I prevent numbers meetings from becoming boring?
Tell stories with the numbers and make them visual. '€200 loss' becomes 'we lost enough to buy a new chef's knife'. Use colors, charts, and concrete comparisons everyone can picture.
⚠️ EU Regulation 1169/2011 — Allergen Information — https://eur-lex.europa.eu/eli/reg/2011/1169/oj
The allergen information on this page is based on EU Regulation 1169/2011. Recipes and ingredients may vary by supplier. Always verify current allergen information with your supplier and communicate this correctly to your guests. KitchenNmbrs is not liable for allergic reactions.
In the UK, the FSA enforces allergen regulations under the Food Information Regulations 2014.
📚 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 →