Why do your best cooks resist the very tools designed to make their lives easier? They've seen too many "improvements" that just meant more work and confusion. Show them the difference through experience, not explanations.
Start with their biggest frustrations
Employees deal with unclear situations daily that cost time. Start there:
- "How many grams of meat should go on this plate?" - endless discussions
- "Is this still good?" - guessing about expiration dates
- "Why are we out of salmon?" - nobody knows
- "Chef says differently" - different versions of the same recipe
💡 Example:
At restaurant De Eik, they debated portion sizes every single day:
- New employee: 300g steak
- Experienced cook: 250g steak
- Chef (when present): 275g steak
Result: inconsistent plates, unhappy guests, arguments every shift. Time lost per discussion: 5 minutes.
Let them feel the difference, don't explain it
People believe what they experience, not what you tell them. Set this up deliberately:
Week 1: Do it the way you always have
Let frustrations happen naturally. Count how many times there's discussion about:
- Recipes ("what was it again?")
- Portion sizes ("I think it was more")
- Temperatures ("did we measure this yesterday?")
- Inventory ("who ordered this?")
Week 2: Introduce the system
Now they've got something to compare against.
⚠️ Watch out:
NEVER promise "this will solve everything". Employees are skeptical about new systems. Let them discover that it works on their own.
Start with one thing that helps immediately
Don't roll out everything at once. Pick something they wrestle with daily:
Option 1: Recipes
If there's constant debate about "how did we make this again?"
Option 2: Temperature registration
If there's ongoing stress about HACCP checks
Option 3: Food costs
If the chef frequently asks "can we still make this at this price?"
💡 Example:
Restaurant Luna focused solely on temperature tracking because an inspection was approaching:
- Old way: paper checklist, often forgotten, frantic searching during inspection
- New way: phone out, temperature logged, finished
- Time saved daily: 10 minutes
- Inspection stress: eliminated
Team reaction: "Actually, this is pretty useful."
Make the time savings visible
Actually count the minutes saved and share this with your team. It's the kind of thing you only learn after closing your first month at a loss - every minute matters more than you think:
Before:
- Hunting down recipe in notebook: 3 minutes
- Arguing about portion size: 5 minutes
- Scribbling temperature on paper: 2 minutes
- Finding where that paper went: 2 minutes
Now:
- Opening recipe on phone: 30 seconds
- Portion size is right there: 0 seconds debate
- Logging temperature: 1 minute
- Everything in one spot: 0 seconds hunting
Time saved per shift: 11 minutes
Per week (6 shifts): 66 minutes = 1 full hour
Give them ownership
Let employees input and refine recipes themselves. Then it becomes their system, not your system that they're forced to use.
💡 Example:
Assign each cook 2-3 recipes to input:
- "You make the best carbonara - can you enter it?"
- "Double-check if the portion size matches how you actually make it"
- "If something looks wrong, just fix it"
Now it feels like their recipe collection, not a system monitoring them.
Celebrate the small wins
Call out explicitly when the system helped:
- "Notice how we didn't argue about portion sizes today?"
- "All temperatures are already logged - no scrambling around"
- "New guy could jump right in with those recipes"
Involve them in improvements
Ask for feedback regularly and make adjustments:
- "What's clunky about this system?"
- "How could we streamline this?"
- "Which recipes are we still missing?"
Tools like KitchenNmbrs work best when they see their suggestions implemented.
How do you introduce a system without resistance? (step by step)
Observe and count frustrations
Spend one week deliberately counting: how many discussions about recipes, portions, temperatures? How much time is spent searching for information? Note concrete times and situations.
Choose one pain point to start with
Tackle the biggest daily irritation. Not everything at once. If temperatures cause the most hassle, start there. Let the team experience that this one thing now goes more smoothly.
Give ownership to the team
Let employees enter and adjust recipes themselves. Ask their opinion and adjust the system based on their feedback. That way it becomes their tool, not your control instrument.
✨ Pro tip
Pick your most enthusiastic cook and spend 15 minutes with them on a Tuesday afternoon (never during rush). Let them log just 3 recipes and watch them become your biggest advocate within 48 hours.
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 employees claim they don't have time for a new system?
Let them track for one week how much time they waste searching, debating, and re-explaining things. Then they can make a real comparison. Start with something that delivers immediate time savings, like having recipes on their phone instead of digging through a messy notebook.
How do you keep older employees from checking out completely?
Position them as the experts whose knowledge needs capturing. Let them input their recipes and hard-earned experience into the system. Frame it as "preserving their expertise" rather than "learning new technology." Start simple and build gradually.
Should I make system usage mandatory from day one?
Absolutely not - start with willing volunteers only. Let them experience real benefits and naturally share success stories with skeptical colleagues. Forced adoption breeds resentment, but genuine enthusiasm spreads organically when the system truly delivers value.
📚 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 →