Your team already spots the problems that numbers reveal later. They see waste happening, notice which dishes slow down service, and know when processes break down. The challenge isn't getting them to see issues—it's getting them to share solutions.
Why team members often don't think along
Your staff witnesses kitchen problems firsthand every shift. They know which dishes create excessive prep time, where ingredients get wasted, and which workflows cause bottlenecks. But many view financial data as management territory.
- They assume they lack financial expertise
- Fear of suggesting something incorrect holds them back
- They're unsure if input is actually wanted
- Numbers feel like personal performance criticism
⚠️ Watch out:
Don't frame numbers as blame. Position them as opportunities for collaborative improvement.
Make numbers understandable for your team
A 38% food cost means nothing to your line cook. But "we're losing €1.80 per plate" creates immediate understanding.
- Convert percentages to daily/weekly euro amounts
- Explain the business impact in concrete terms
- Connect data to their actual kitchen experiences
- Clarify why improvements benefit everyone
💡 Example:
Instead of: "The carbonara has a 38% food cost"
Try: "Each carbonara costs us €1.50 more than it should. With 35 sold weekly, that's €2,730 annually."
Now the stakes become crystal clear.
Create a safe environment for input
People share ideas only when they feel secure. Frame discussions around problem-solving, not fault-finding.
- Open with: "The data shows this pattern—what's your take?"
- Ask about their observations: "Have you noticed this happening?"
- Acknowledge every contribution, even unusable ones
- Demonstrate genuine consideration of their suggestions
Use their practical knowledge
Your team knows details that spreadsheets can't capture. Which vendors consistently deliver late. Which ingredients spoil fastest. Which recipes create inconsistent results.
💡 Example conversation:
"Our salmon dishes show high waste costs. What happens with salmon prep in your experience?"
- "Supplier Y's salmon has way more unusable trim"
- "We discard portions that don't look presentation-ready"
- "Weekend orders often exceed actual sales"
These insights provide actionable improvement targets.
Involve them in finding solutions
After identifying issues, solicit their solution ideas. They'll implement changes, so they understand what's actually workable. Based on real restaurant P&L data, employee-suggested solutions typically show 40% better adoption rates than top-down mandates.
- "How could we tackle this differently?"
- "Which approach would fit your workflow?"
- "What resources would help fix this?"
- "Who's interested in leading this improvement?"
Give ownership and recognition
When someone contributes a valuable idea, make them the project owner. Credit their contributions publicly.
💡 Example:
"Marcus's supplier switch for salmon saved us €285 last month. This is exactly the kind of problem-solving we need from everyone."
Public recognition motivates others to contribute ideas.
Make it a routine
Schedule regular, brief team discussions about performance data and results. Not emergency meetings—routine check-ins.
- Weekly 15-minute sessions: celebrate wins, identify opportunities
- Highlight positive outcomes from team improvements
- Actively seek input on emerging challenges
- Demonstrate how their suggestions create measurable impact
How do you organize an effective numbers conversation with your team?
Prepare the numbers
Translate percentages into concrete euro amounts per day or week. Choose 1-2 concrete examples everyone can work with. Make it recognizable to their daily work.
Start with recognition
Begin with what's going well. Thank the team for their effort. Position the conversation as 'getting better together', not as 'this is going wrong'.
Share the numbers transparently
Show the concrete numbers and explain what they mean. Use examples from their own work. Ask: 'Do you recognize this?'
Ask about their experience
Let the team tell you what they see in practice. Really listen to their input. Ask follow-up questions: 'When do you notice this the most?'
Brainstorm solutions together
Explicitly ask for their ideas. Write down all suggestions, even the crazy ones. Discuss what's practically feasible. Let them choose which solution they want to try.
✨ Pro tip
Share one concrete success story first: "Remember when Sarah suggested changing our potato supplier last quarter? That single idea saved us €180 per month." Real examples with specific savings motivate future participation.
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 says numbers aren't their thing?
Emphasize you need kitchen expertise, not math skills. Their hands-on knowledge of daily operations is far more valuable than calculation abilities.
How often should I discuss numbers with the team?
Begin with monthly 15-20 minute sessions. As comfort grows, increase to weekly discussions. Keep meetings focused and practical.
What if someone suggests an impractical solution?
Appreciate their engagement and explain the constraints. Ask follow-up questions like 'What would make this feasible?' to keep them involved in the problem-solving process.
Should I share all financial numbers with staff?
Only share data relevant to their roles. Food costs for dishes they prepare, waste they can control. Keep broader P&L information confidential.
How do I ensure good ideas actually get implemented?
Create specific action plans with clear owners and deadlines. Review progress in subsequent meetings and celebrate successful improvements, however small.
What if my team becomes too focused on cutting costs at the expense of quality?
Set clear boundaries about maintaining standards while improving efficiency. Emphasize that solutions should reduce waste without compromising the guest experience.
📚 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 →