The Human Firewall: Why Your Best Employees Become Your Biggest Resistance — And How to Turn Them Into Champions
There is an old story about a king and his gardener.
The king decided to build a new palace. Grand. Modern. A monument to progress. He summoned architects from distant lands. He imported marble from mountains he had never seen.
But when construction began, one man stood in the way.
The royal gardener. Forty years in service. He had planted every tree in the old palace grounds. He knew the name of every flower. The birds came to him each morning, expecting seeds from his pockets.
The king was confused. “You are my most loyal servant. Why do you oppose the new palace?”
The gardener’s answer was simple: “Because, my king, I am not opposing your future. I am protecting everything I helped you build.”
The Paradox Nobody Talks About
Here is a truth that will make you uncomfortable:
The employees who resist your ERP project the most are often your best employees.
Not the lazy ones. Not the troublemakers. Not the ones counting days to retirement.
No. The resisters are your stars. Your experts. Your institutional memory. The people who hold your operations together with knowledge that exists nowhere except inside their heads.
This is the paradox that destroys ERP projects.
Because when leadership sees resistance, they see a problem to be solved. An obstacle to be removed. A mindset to be “managed.”
But resistance is not the disease.
Resistance is the symptom.
And until you understand what it’s a symptom of, you will never heal it.
What Resistance Really Means
Let me tell you about Fatima.
Fatima was a production planner at a manufacturing company in Abu Dhabi. Twenty-two years with the company. She started as a data entry clerk. Worked her way up. Learned every machine, every product, every customer’s quirks.
When orders came in, Fatima didn’t just schedule them. She orchestrated them. She knew that Customer A always changed quantities at the last minute, so she built buffer. She knew that Machine 7 ran slow on humid days, so she adjusted timing. She knew that the night shift supervisor was slower than the morning one, so she loaded complexity accordingly.
None of this was in any system. It lived in Fatima’s mind. It lived in her notebooks. It lived in twenty-two years of pattern recognition that no algorithm could replicate.
Then the ERP project came.
The consultants arrived with their process maps and their “best practices.” They looked at Fatima’s notebooks and smiled politely. They talked about “standardization” and “eliminating tribal knowledge.”
Fatima heard something different.
She heard: “Everything you’ve built doesn’t matter.”
She heard: “Your expertise is a problem to be solved.”
She heard: “You are obsolete.”
And so Fatima resisted. Not loudly. Not obviously. She simply… stopped helping. She answered questions with minimum words. She attended training but learned nothing. She waited — patiently, quietly — for the project to fail.
This is what resistance really means:
It is not stubbornness. It is grief.
It is the grief of someone watching their life’s work be dismissed. Their identity be threatened. Their value be questioned.
And grief, unacknowledged, turns to anger. Anger turns to sabotage. Sabotage turns to failure.
The Five Faces of Resistance
Resistance wears many masks. Learn to recognize them.
Face #1: The Guardian
Who they are: Long-tenured experts. Process owners. The people everyone calls when something breaks.
What they say: “This won’t work here. We tried something similar in 2015.”
What they mean: “I’ve spent years building something that works. You’re about to destroy it without understanding why it works.”
What they need: To be heard. To be involved. To have their knowledge captured and honored — not discarded.
Face #2: The Skeptic
Who they are: Analytical minds. Often in finance or engineering. They’ve seen initiatives come and go.
What they say: “Show me the ROI. What’s the evidence this will work?”
What they mean: “I’ve been burned before by promises. I need proof, not enthusiasm.”
What they need: Data. Case studies. Honest acknowledgment of risks alongside benefits. Respect for their intelligence.
Face #3: The Overwhelmed
Who they are: High performers already stretched thin. People carrying too much.
What they say: “I don’t have time for this. I have a job to do.”
What they mean: “You’re asking me to do my regular work AND learn a new system AND attend training AND participate in testing. Something will break. It will probably be me.”
What they need: Realistic workload adjustment. Temporary relief from other duties. Acknowledgment that change takes time and energy.
Face #4: The Fearful
Who they are: Often older employees, or those with narrower skill sets. People who quietly worry about their relevance.
What they say: Very little. They nod in meetings. They agree publicly.
What they mean: “If the system can do what I do, what happens to me?”
What they need: Reassurance — genuine, not performative. A clear picture of their role after go-live. Investment in their growth.
Face #5: The Politician
Who they are: Middle managers. People whose power comes from controlling information or access.
What they say: “We need to be careful about change. Let’s form a committee.”
What they mean: “This new system threatens my position. If everyone has access to information, why do they need me?”
What they need: A new source of value. A role in the new world that preserves their status. Or, sometimes, honest confrontation.
The Mistake Leaders Make
When executives encounter resistance, they typically respond in one of three ways.
All three are wrong.
Mistake #1: Ignore It
“They’ll come around once they see the benefits.”
No. They won’t. Ignored resistance doesn’t dissolve. It calcifies. It becomes culture. And cultures are nearly impossible to change.
Mistake #2: Overwhelm It
“This is happening whether they like it or not. Get on board or get out.”
Sometimes this seems to work. People comply. They show up. They click the buttons.
But compliance is not adoption. A person can use a system while actively undermining it. They can follow the process while quietly maintaining shadow spreadsheets. They can attend every training while learning nothing.
You cannot force someone to care.
Mistake #3: Dismiss It
“The resisters are just negative people. We’ll work around them.”
This is perhaps the most dangerous mistake. Because often the resisters are your most valuable people. They resist precisely because they care deeply about the work.
When you dismiss them, you lose their knowledge. Their relationships. Their ability to make the impossible happen when systems fail — and systems always fail eventually.
The Path to Championship
So what works?
I have seen resistance transform into championship. Not once — many times. Here is the path.
Step 1: Listen Before You Lead
Before the project begins — before the vendor is selected, before the budget is approved — go talk to your people.
Not to inform them. To understand them.
Ask:
- “What works well today that we must not lose?”
- “What frustrates you that you hope we can fix?”
- “What worries you about this change?”
- “What would make this successful in your eyes?”
Write down what they say. Not to argue. Not to correct. Just to capture.
This act of listening does something powerful: it transforms people from subjects of change to authors of change. They are no longer being changed. They are participating in change.
Step 2: Honor the Past
Every system being replaced was once someone’s achievement.
The ERP you’re replacing? Someone worked nights and weekends to implement it. Someone fought for the budget. Someone trained the users. Someone has been maintaining it for years.
If you treat the old system as garbage to be discarded, you are treating those people’s work as garbage. They will feel it. They will resent it. They will resist.
Instead, honor what was.
“This system served us well for fifteen years. It got us to where we are today. And now we need to grow beyond what it can offer.”
Acknowledge the past before you build the future.
Step 3: Give Resistance a Role
Here is a counterintuitive strategy: put your biggest resisters on the project team.
Yes, really.
The Guardian who knows every workaround? Make them a subject matter expert. Their job is to ensure the new system captures the critical knowledge from the old one.
The Skeptic who questions everything? Make them responsible for validation. Their job is to pressure-test every claim, every assumption, every promise.
The Fearful who worry about their future? Train them first. Make them the trainers for others. Give them a new source of value.
When resisters have a role, they have ownership. When they have ownership, they have investment in success.
Step 4: Show, Don’t Tell
Words are cheap. Everyone promises “this time will be different.” Nobody believes it anymore.
So stop talking. Start showing.
Build a pilot. A proof of concept. A small win that demonstrates real value.
Let the skeptics see it working. Let the fearful use it in a safe environment. Let the guardians verify that their knowledge has been captured.
One demonstration is worth a thousand presentations.
Step 5: Address the Real Fear
Beneath every resistance is a fear. Usually one of three:
Fear of incompetence: “I won’t be able to learn this. I’ll look stupid.”
Fear of irrelevance: “The system will replace me. I’ll lose my job.”
Fear of failure: “This will go wrong. I’ll be blamed.”
These fears are rarely spoken aloud. But they drive behavior.
Address them directly.
“This system is new to everyone. Struggling is normal. There’s no judgment here.”
“Your job isn’t going away. But your role will evolve. Let me show you what that looks like.”
“We will make mistakes. That’s part of implementation. What matters is how quickly we learn and adapt.”
Step 6: Celebrate the Converts
When a resister becomes a champion, celebrate it loudly.
Not to embarrass them. To honor them.
“Fatima was skeptical at first — and honestly, her skepticism made us better. She asked the hard questions. She demanded proof. And now she’s one of our strongest advocates. That’s the kind of honest engagement we need.”
This does two things.
First, it validates the convert. It says: your resistance was valuable, your conversion is respected.
Second, it signals to other resisters: there is a dignified path from opposition to support. You don’t have to lose face. You don’t have to admit you were “wrong.” You can evolve.
The Change Champion Framework
I use a framework called BRIDGE to convert resistance to championship.
B — Believe in Their Value
Start from the assumption that resisters are valuable people with valid concerns. If you don’t genuinely believe this, nothing else will work. People sense contempt.
R — Recognize Their Expertise
Explicitly acknowledge what they know. Capture it. Document it. Show them their knowledge matters.
I — Involve Them Meaningfully
Not token involvement. Real roles. Real decisions. Real impact on how the system is configured and deployed.
D — Demonstrate Results
Show small wins early. Prove that the new system delivers real value. Let skeptics see evidence.
G — Give Them a Future
Paint a clear picture of their role after go-live. Train them. Invest in them. Show them they matter in the new world.
E — Empower Them to Lead
Turn converts into evangelists. Let them train others. Let them speak at town halls. Let them own pieces of the rollout.
The Metrics of Hearts and Minds
How do you know if you’re winning the human battle?
Track these:
The Story of Fatima, Continued
Remember Fatima? The production planner who resisted?
Her project team was smart. They recognized what she represented.
They came to her — not to convince her, but to learn from her. They sat with her for days, documenting every rule in her head, every exception she managed, every trick she used to keep production flowing.
They built those rules into the new system. Not as afterthoughts — as features. “Fatima’s Rules,” they called them internally.
Then they asked her to test. To verify that the system captured what she knew.
At first, she found gaps. Many gaps. And each time she found one, they fixed it. They thanked her for finding it.
Slowly, something shifted.
The system was no longer a threat. It was a vessel. A vessel carrying her twenty-two years of knowledge. A vessel that would preserve what she had built long after she retired.
On go-live day, Fatima wasn’t just present. She was leading. She was the one calming nervous users. She was the one solving problems. She was the one saying, “Trust the system. I helped build it.”
She had become a champion.
Not because anyone convinced her.
Because they honored her.
The Question You Must Answer
Before you proceed with your ERP project, answer this question honestly:
“Do the people who will use this system believe it was built with them, or done to them?”
If the answer is “done to them,” you have work to do.
The good news? It’s not too late. It’s never too late to start listening. To start involving. To start honoring.
The human firewall can become the human accelerant.
But only if you approach it with humility.
Only if you remember that behind every resistance is a human being — with fears, and hopes, and a lifetime of knowledge that deserves respect.
Who’s the “Fatima” in your organization? The expert everyone relies on who might resist the change? What would it take to bring them on board?
Tell me in the comments. These conversations matter.
