Think of number resistance like an iceberg - most of it stays hidden below the surface. Team members who feel threatened by math or fear micromanagement rarely voice concerns directly. Instead, they deflect through humor, cynicism, or dismissive comments that mask deeper anxieties.
Recognizable signs of number resistance
Resistance to numbers rarely shows up directly. People don't admit "I'm terrible at math" or "This scares me". Instead, you'll hear:
- "Numbers always lie anyway"
- "We've done fine without all these calculations until now"
- "That's something for the boss, not for me"
- "Guests come for good food, not spreadsheets"
⚠️ Watch out:
Cynicism about numbers often stems from insecurity. People who feel unsure about their math skills defend themselves by downplaying the importance of calculations.
Observe body language and behavior
Beyond words, behavior reveals resistance too:
- Looking away during explanations about costs or margins
- Arms crossed during number presentations
- Quickly changing the subject from food costs
- "Forgetting" to record temperatures or quantities
- Overdone focus on other tasks during number discussions
💡 Example:
You explain that a dish has 35% food cost. Responses that reveal resistance:
- "Yeah but the flavor is right" (distraction to something else)
- "Sure, whatever" (feigning disinterest)
- "We didn't calculate so precisely back then" (romanticizing the past)
These are all ways to steer conversations away from numbers.
Fear of control and accountability
Much resistance comes from fear that numbers will be used to hold people accountable. From years of working in professional kitchens, I've seen this fear manifest through comments like:
- "Are you going to monitor us on every gram now?"
- "Soon everything gets recorded and I'll be fired if I make a mistake"
- "This is the beginning of the end, now everything gets automated"
This fear makes sense. Many people have experienced numbers being used against them, rather than to help them perform better.
💡 Example:
A chef responds to food cost tracking with: "Are we going to count every onion now?" This seems like a joke, but actually reveals:
- Fear of micromanagement
- Misunderstanding of the purpose of numbers
- Feeling that their craftsmanship isn't trusted
The joke masks real concerns.
How to turn resistance into understanding
Once you recognize resistance, don't push back but look for the underlying concern:
- Acknowledge the concern: "I understand this feels like extra control"
- Explain the purpose: "It's not about monitoring you, but about seeing where we're losing money"
- Make it concrete: "If we know this dish is too expensive, we can adjust the portion instead of lowering quality"
- Involve them in the solution: "You know where waste happens - help me find it"
⚠️ Watch out:
Never force numbers through resistance. That only strengthens opposition. Take time to build trust and demonstrate value.
Small steps, big change
Don't start with complex cost calculations for a resistant team. Begin with something simple that delivers immediate benefit:
- Show how much money goes in the trash
- Calculate what it saves if portions are 10% smaller
- Demonstrate that better portioning creates happier guests (less food waste on plates)
Once people see that numbers help rather than threaten them, resistance disappears naturally.
How do you recognize and address number resistance?
Observe verbal signals
Pay attention to cynical remarks, jokes about numbers, or attempts to avoid the topic. Note which team members often react negatively to number discussions.
Look at body language and behavior
Observe looking away, closed posture, or 'forgetting' to record things. These signals are often clearer than words.
Find the underlying concern
Ask follow-up questions: 'What makes you unsure about this number?' or 'What are you afraid of if we start measuring this?' Often there's fear of control or failure behind it.
Start by showing benefit
Begin with a simple number that delivers immediate benefit, like saving money through less waste. Show that numbers help, not threaten.
Involve the team in solutions
Ask their opinion: 'Where do you think we're losing money?' or 'How would you measure this better?' This makes them co-owners of the numbers.
✨ Pro tip
Track resistance patterns for 2 weeks by noting who makes dismissive comments during cost discussions. You'll spot the 20% of staff creating 80% of the negativity, allowing you to focus your conversion efforts where they'll have maximum impact.
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 someone openly says numbers are nonsense?
Don't argue but ask about the experience behind it: 'Have you had bad experiences with numbers?' Often there's a story of data being misused for control rather than improvement.
How long does it take for resistance to disappear?
That depends on the person and their experience. Some come around after one success story, others need months. Patience and consistently showing benefit matter most.
Should I force resistant team members to participate?
Forcing backfires and strengthens resistance. Better to find volunteers who are enthusiastic, so others see the benefit and join naturally.
What if the chef themselves shows resistance to numbers?
Start with respect for their experience: 'You've cooked amazingly for years without these numbers.' Then show how numbers can support their cooking, not replace it.
How do I prevent numbers from being seen as a control tool?
Never use numbers to hold people accountable, always to solve problems. Say: 'This dish loses money, how can we fix that?' instead of 'Your portion is too big.'
What's the difference between playful teasing and actual resistance?
Playful teasing is brief and followed by engagement. Resistance involves repeated deflection, consistent avoidance, or escalating negativity during number discussions.
How do I handle team members who mock others for caring about food costs?
Address it privately first - explain how their comments undermine team goals. If it continues, make it clear that respect for all approaches is non-negotiable in your kitchen.
📚 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 →