BETA APP IN DEVELOPMENT HACCP and more are available in your dashboard — currently in beta, so minor bugs may occur. The updated app with full integration is coming soon.
📝 Team & numbers · ⏱️ 2 min read

How do I combine team feedback with system data into one story?

📝 KitchenNmbrs · updated 14 Mar 2026

Running a restaurant kitchen is like conducting an orchestra—every instrument needs to play in harmony. Your system gives you the sheet music (the numbers), but your team tells you how it actually sounds in practice. Together, they create the full symphony of what's working and what's falling flat.

Why numbers alone aren't enough

Your system shows that carbonara has a 28% food cost and sells consistently. Looks great on paper, right? But your chef mentions it takes 15 minutes longer than other pasta dishes because of that finicky cream sauce, backing up the entire line during dinner rush.

💡 Example:

System data says:

  • Steak: 32% food cost, 45 sold this week
  • Salmon: 35% food cost, 23 sold this week

Team feedback:

  • Steak: "Guests often ask for medium-rare, we nail it"
  • Salmon: "Lots of returns, guests find it dry"

Conclusion: Steak is the winner, salmon needs adjusting

Collect team feedback systematically

Schedule brief weekly check-ins with your kitchen crew. Don't wing it—ask targeted questions about:

  • Prep time: Which dishes eat up the most time?
  • Consistency: What's hardest to execute perfectly every time?
  • Waste patterns: Where do they see ingredients going to waste?
  • Customer reactions: What praise or complaints filter back from the dining room?

⚠️ Watch out:

Don't ask "what do you think of dish X?". That gives vague answers. Ask specifically: "How long does dish X typically take?" or "How many grams do you throw away per portion?"

Link feedback to your data

Now comes the magic—matching your system numbers with what your team actually experiences. This is the kind of thing you only learn after closing your first month at a loss, wondering why profitable-looking dishes killed your efficiency.

💡 Example connection:

System: Pesto pasta sells 60x per week, food cost 25%

Team: "Fastest dish, always good, guests often order extra"

Action: Promote this dish more on your menu

Make decisions based on both

Armed with this complete picture, you can take smart action:

  • Promote: Dishes with solid numbers AND positive team feedback
  • Adjust: Dishes with good numbers but team struggles
  • Remove: Dishes with poor numbers AND negative feedback
  • Investigate: Dishes with poor numbers but positive feedback

💡 Real-world example:

Risotto has 38% food cost (too high) but team says: "Guests love it, always ask for it"

Solution: Raise the price by €3 instead of removing the dish

Result: 31% food cost, happy guests, happy team

Document your findings

Track what you discover. For each dish, record:

  • Food cost percentage from system
  • Sales numbers per week
  • Team feedback summarized
  • Action you're going to take

Tools like KitchenNmbrs let you attach notes to each dish, keeping this intel handy for menu planning sessions.

How do you combine team feedback with data? (step by step)

1

Gather your system data

Pull from your system the numbers of your 10 best-selling dishes: food cost %, sales numbers and revenue per dish. Print it out or put it in an overview.

2

Organize a team meeting

Schedule 30 minutes with your kitchen staff. Go through your list systematically and ask per dish about prep time, difficulty level and guest feedback. Write everything down.

3

Analyze and link the information

Put your numbers next to the feedback. Make three lists: dishes to promote, adjust, or remove. Focus first on your top 5 best-selling dishes.

✨ Pro tip

Focus your first review on the top 5 dishes that generate 70% of your weekly revenue. Once you've aligned team feedback with system data on these core items, you've optimized the majority of your kitchen's performance.

Calculate this yourself?

In the KitchenNmbrs app you can do this in just a few clicks. 7 days free, no credit card.

Try KitchenNmbrs free →

Was this article helpful?

Share this article

WhatsApp LinkedIn

Frequently asked questions

How often should I collect team feedback?

Every 2-3 weeks hits the sweet spot. More frequent and you'll overwhelm your team with questions. Less often and you miss crucial shifts in kitchen dynamics or customer preferences.

What if my team has different opinions about the same dish?

Let the numbers be your tiebreaker. If sales and food costs look solid, test both approaches for a week and see which generates better customer response.

Should I also include feedback from the serving staff?

Absolutely—servers are your direct line to customer sentiment. Ask them specifically about which dishes get compliments, complaints, or are easiest to upsell.

What if the numbers are good but the team is negative?

Dig deeper into why they're struggling with it. Maybe it's a prep issue or timing problem. Often small tweaks can keep your margins intact while making the team's job easier.

ℹ️ This article was prepared based on official sources and professional expertise. While we strive for current and accurate information, the content may differ from the most recent regulations. Always consult the official authorities for binding standards.

📚 Sources consulted

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.

JS

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.

🏆 8 years kitchen manager at 1NUL8 Group Rotterdam
Expertise: food cost management HACCP kitchen management restaurant operations food safety compliance

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 →
Disclaimer & terms of use

Table of Contents

💬 in 𝕏