A chef spends €300 monthly on management software, enters data religiously for eight weeks, then discovers his team hasn't opened the app once. Sound familiar? You're not alone - this disconnect between investment and adoption plagues restaurants everywhere.
Does this scenario sound familiar?
You've purchased a management system. The first few weeks you're enthusiastic and fill everything in neatly. You see your food cost, your temperatures are registered on time, and you finally have an overview. But after a month you notice you're the only one still looking at it.
Your team does register the temperatures (if you insist), but they don't use the information. They don't look at the food cost of their dishes. They don't check if purchases match sales. The system becomes an administrative burden instead of a tool.
⚠️ Watch out:
This pattern emerges within 4-6 weeks of implementation. If your team isn't working with it by then, it only gets harder.
Why your team ignores the system
There are usually three reasons why your staff doesn't look at the system:
- They don't see the benefit for themselves - It seems like extra work without reward
- They don't understand what the numbers mean - A food cost of 32% means nothing to them
- They're not involved in the consequences - Whether it's profitable is "your problem"
💡 Example:
Your sous-chef sees that the steak has a food cost of 38%. For him this means:
- "That's a number in an app"
- He doesn't know that 38% is too high
- He doesn't know that this costs €2,400 per month
- He doesn't know that this threatens his own job
Make the numbers personally relevant
The problem isn't that your team doesn't understand the numbers. The problem is that they don't feel the consequences. You need to link the numbers in the system to their daily work.
Instead of: "The food cost is in the system"
Say: "If we lower the food cost of the steak by 3%, we can raise your salary"
Instead of: "Register the temperatures"
Say: "If we get a health inspection without registrations, they can shut us down"
💡 Example - Weekly team meeting:
"Last week we sold 120 steaks. The ingredients cost €9.20 per steak instead of €8.50. That's €84 this week, €4,368 per year. With that we can pay for an extra team outing."
Give ownership to your team
People use systems if they feel ownership of them. Give each team member responsibility for a specific part:
- Sous-chef: Food cost of the 5 most popular dishes
- Kitchen staff: Track waste and leftovers
- Dishwashing/prep: HACCP temperatures and delivery checks
Make it competitive. Who keeps their food cost under control? Which shift has the least waste? People love a bit of competition, especially if there's a small reward involved. This is one of the most common blind spots in kitchen management - owners think staff will naturally care about numbers without creating personal stakes.
💡 Example - Monthly challenge:
"Whoever keeps the food cost of their dishes under 30% this month gets a €50 bonus. Last month that was Lisa and Marco."
Train your team to read numbers
Your team doesn't know what the numbers mean because nobody has explained it. Take 15 minutes per week to explain one number.
Week 1: What is food cost and why is 30% better than 35%?
Week 2: How much does 5 grams of extra butter cost per year?
Week 3: Why do we register temperatures?
Week 4: What happens if we buy too much?
Use concrete examples from your own kitchen. No theory, just practice.
If it doesn't work: drastic measures
Sometimes you need to take a harder line. If your team still isn't cooperating after 2 months of training and explanation, you have two options:
- Make it mandatory: No salary payment without complete HACCP registrations
- Replace people: Anyone who won't work with the systems doesn't fit your team
⚠️ Watch out:
This is a last resort. Try motivation and training first. But if someone consistently refuses to cooperate with running the business, it will ultimately cost you more than finding a new employee.
Adapt the system to your team
Maybe the problem isn't just your team, but how you're using the system. Some restaurants make it too complicated:
- Too much data: Focus on 5 important numbers, not 50
- Too complex: Start with temperatures, add food cost later
- No feedback: Show what happens with the information
You can start with only HACCP tasks. Once that's routine, add recipes. If that works, move to cost calculation. Step by step.
💡 Example - Phased implementation:
Month 1: Register temperatures only
Month 2: Add delivery checks
Month 3: Enter recipes
Month 4: Calculate food cost
This way it's not an overwhelming change, but a gradual improvement.
How do you get your team on board with the system? (step by step)
Analyze why they're not using it
Ask your team directly why they don't look at the system. Is it too complicated? Don't they see the point? Don't they understand the numbers? Only if you know the real reason can you fix it.
Make the consequences personal and concrete
Explain what the numbers mean for their own situation. A food cost of 35% instead of 30% costs you €500 per month - money that could have gone to salary increases or team outings. Make it tangible.
Give everyone their own responsibility
Divide the tasks: one person tracks waste, another tracks food cost of popular dishes, a third handles HACCP registrations. Ownership creates involvement.
Train one number or concept weekly
Take 15 minutes each week to explain one part. What does food cost mean? Why do we register temperatures? Use examples from your own kitchen, not theory.
Reward desired behavior and correct unwanted behavior
Give compliments when someone is doing well with the numbers. Organize a small competition. And if someone consistently refuses to cooperate after training and explanation, take action.
✨ Pro tip
Check your system usage logs every 2 weeks - most platforms show who's actually logging in. If someone hasn't touched it in 10 days, have a one-on-one conversation immediately.
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 they don't have time for the system?
Then they're using it wrong. Registering temperatures takes 2 minutes a day. Checking food cost takes 5 minutes a week. If it takes more time, train them better or simplify the process.
Should I fire people who refuse to work with systems?
Only as a last resort. Try 2 months of intensive training and motivation first. But if someone refuses after that, it will cost you more than finding a new employee.
How do I motivate older employees who don't like computers?
Focus on the why, not the technology. Explain that registering temperatures protects against fines and closure. That tracking food cost leads to better salaries. The app is just the tool.
Can I make the system mandatory without demotivating people?
Yes, if you explain it well. Don't say "you have to", say "this helps all of us get better". Explain the benefits before you set rules.
What if only I understand the numbers?
Then you've failed to transfer knowledge. Take time to train your team. A restaurant runs on the team, not one person. If only you understand the numbers, you have a vulnerable business.
How often should I discuss the numbers with my team?
Weekly the important numbers (top food cost items, waste, temperatures). Monthly the big picture (total purchases vs sales, trends). Daily only for problems or deviations.
What's the biggest mistake when introducing new kitchen management software?
Dumping everything on your team at once without proper training. Start with one simple task, master it completely, then gradually add more features over 3-4 months.
📚 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.
Make better decisions with real numbers
Should you change your menu? Raise prices? Test a new concept? KitchenNmbrs simulates scenarios with your own data. Try it free for 14 days.
Start free trial →