Your Team Said "Mafan". Here's What That's Actually Costing You.

We're six weeks into building an inventory system for a Malaysian snack manufacturer. The boss is bought in — he's felt the pain personally, signed off in one meeting, wrote the cheque. But half his ops team is quietly resisting. Not with words, with behavior. "I'll enter it later." "Let me write it down first." "The old way was fine." If you've ever been the boss who approved the change and then watched it stall, this one's for you.

The Business

A Malaysian snack manufacturer we're working with right now. Multiple SKUs — prawn crackers, fish chips, seaweed crisps — each flowing from raw material to cooking to packing to delivery. On paper, a clean operation. In practice, everything runs on paper DO and PO forms, WhatsApp photos of stock counts, and one Excel file that three people edit on different laptops.

If you read our story about the travel agency, you'll notice the same shape — different industry, same pain.

Why Malaysian SME Staff Resist New Systems

Here's what gets lost in the paper flow.

A supplier delivers 95kg of palm oil when the PO said 100kg. Nobody notices for two weeks, because nobody cross-checks DO against PO until month-end. That's RM80 gone, quietly, every time.

Month-end reconciliation takes three days because someone's DO is missing, someone else's photo is blurry, and the Excel file has three versions with different numbers.

Stock variance sits at 8% and nobody can explain where it went. Is it shrinkage? Theft? Mis-counted? Nobody knows, so nobody can fix it.

The boss knew all of this. He signed off in one meeting. He wrote the cheque. That was the easy part.

What happened next is the actual story.

The Ops Manager Said Mafan

Not hostile. Just behavioral. The system is there. It works. But there's always a reason not to use it right now.

Three patterns we see, again and again:

• "I'll enter it later." They never do. By the end of the day, the details are fuzzy. By the end of the week, the details are gone.
• "Let me write it down first." Paper becomes the real record. The system becomes a backup. Then the backup gets abandoned because it's redundant.
• "The old way was fine." The old way is what created the three-day month-end reconciliation you're paying to fix. But the old way is muscle memory. Change is discomfort.

Each excuse is individually rational. Collectively, it kills adoption.

The Real Mafan Is What They're Defending

Here's the reframe that changes the conversation.

Every small mafan hides a bigger mafan:

• "Extra 2 clicks per DO" → Three days of month-end reconciliation
• "Learn new screens" → Arguing with a supplier about quantity delivered three weeks ago
• "Enter it now" → Reconstructing what happened from memory next Tuesday

The mafan they're avoiding is small, daily, and visible. The mafan they're defending is big, occasional, and invisible until month-end.

One is felt every time someone types. The other is felt once a month — but when it's felt, the whole operation stops. Making this visible is the first step. You can't change behavior if both sides of the trade-off aren't on the table.

Mafan Isn't Laziness — It's Loss Aversion

Something worth saying plainly: your ops lead isn't lazy.

They're protecting the one system they know works — their muscle memory. The paper system. The WhatsApp photos. The Excel file they've edited a thousand times.

A new system means risk. Risk of looking slow in front of the boss. Risk of making a mistake during the transition. Risk of forgetting a field and getting called out. The risk of looking incompetent is immediate. The benefit of cleaner data is abstract and weeks away.

This is the same calculation any of us would make in their position.

The fix isn't to shame the behavior. The fix is to change the math.

If you're in this exact moment right now — signed off, team dragging feet — we do 30-minute diagnostic calls. No pitch.

What We're Learning, Live

Four tactics we're trying right now. One takes ten minutes and you can do it tomorrow morning.

1. Ask your ops lead which single field is the most mafan — just that one. Ten minutes. They'll tell you without hesitation. Now you have a priority list ranked by the people whose hands are on the work.
2. Make the most frequent action faster than paper, not just equivalent. If it takes the same time as writing in the book, mafan wins. Parity isn't enough.
3. Don't train everyone. Win one ops person first. One person who gets it, uses it, and tells the others it's actually better. That's worth more than any onboarding session.
4. Measure adoption weekly, not at go-live. Silence from the team isn't success — it's drift. If usage dips in week 3, act in week 3. Don't find out at month-end.

If This Sounds Like Your Business

Before you close this tab, be honest with yourself:

• Your team agrees the current way is painful, but nothing changes
• Every new tool gets "tried" for two weeks and quietly abandoned
• You've paid for software that's sitting mostly unused
• Month-end is a predictable disaster you've learned to live with
• Your best staff are burning out on work a system should handle

If two or more apply, you're in the mafan trap. And the longer you sit in it, the more expensive it gets — because the cost isn't just the software you've already paid for. It's the reconciliation time, the supplier arguments, the decisions you're making with data you can't trust.

What Actually Gets You Through It

Three rules we now follow before writing code:

1. Start with the field they hate most.
2. Win one person before you train ten.
3. Watch adoption weekly, not at launch.

None of this is about the software. All of it is about the math your team is doing in their heads every time they choose paper over the system. Change the math, change the outcome.

If you're trying to cost out a build like this, we wrote a 2026 breakdown of what production tracking systems actually cost in Malaysia — including the worked example for a 30-person factory like the one in this story.

If you've said yes to digitalizing and you're watching it stall — that's the hardest moment, and most founders go through it alone. A 30-minute conversation is free. We've just been in this fight; we'll tell you what's working.