Why Employees Resist ERP Change (and What To Do About It)

Most project teams treat resistance to a new ERP system as a discipline problem: people just need to get on board. But resistance is rarely about attitude. It’s usually a rational response to something the implementation hasn’t addressed yet, like a threat to someone’s competence, a sense that the change was done to them rather than with them, a gap in communication, or a mismatch between what leaders say and what they actually do. Understanding which of these is driving the pushback matters more than pushing harder against it.

The Competence Threat: When New Systems Threaten Old Expertise

Employees who spent years becoming the person everyone turned to under the old system suddenly find themselves back at square one. That’s not a small thing. Expertise is part of how people see their value at work, and a new ERP implementation can quietly erase it overnight.

This is why resistance often shows up hardest among your most experienced people, not your newest hires. They have the most status to lose. The fix isn’t more training hours. It’s giving people permission to be slow at first without penalty, pairing early adopters with those still struggling, and recognizing progress on the new system rather than expecting immediate mastery.

When Change Feels Imposed Rather Than Owned

Workflows redesigned by a project team or outside consultants can feel like something that happened to employees rather than something they helped shape. That distinction drives whether people comply quietly or find quiet ways around the new process.

I saw this firsthand as a warehouse manager during an ERP implementation. The project team redesigned several of my team’s core daily processes, and none of that redesign involved a conversation with me about how it would land on my team. I found out what was changing around the same time my crew did. There was no chance to flag how the new processes would affect our day-to-day work, no opportunity to build any buy-in before go-live. All I could do was try to explain changes I barely understood myself, then absorb the frustration when it didn’t go smoothly. Being close enough to the work to see the impact coming, but too far outside the implementation to do anything about it, is its own particular kind of frustration.

Give frontline managers and employees a real channel to flag concerns and treat that input as part of how the implementation gets shaped, not paperwork to file away. When you adjust something because of what people tell you, say so. That single acknowledgment does more to reduce resistance than another all-hands presentation.

Transformation is not easy, but it doesn’t have to be impossible. Take control of your project’s success today and schedule a free 30-minute consultation to find out how Victoria Fide can equip you for transformational success.

The Communication Vacuum

Go-live is often when communication drops off the most, right as project teams get buried in technical fires. Employees notice the silence and fill it with assumptions, usually not generous ones. If nobody explains what’s happening, people will decide for themselves that this means layoffs, or that their role is being phased out.

Keep a fixed communication cadence through the entire implementation, independent of how the technical side is going. Be explicit about what’s changing and, just as important, what isn’t. And treat communication as two-way. A steady stream of updates that never makes room for questions isn’t much better than silence.

The Leadership Say-Do Gap

Employees read behavior, not slogans. A leader who champions the new system in a town hall but still runs their own numbers through the old spreadsheet is sending a clearer message than anything said from a podium. So is a team whose performance metrics haven’t been updated to reflect the new process.

If leadership wants adoption, leadership has to visibly use the new system themselves, in front of the people they’re asking to change. And the metrics that get reported up the chain need to reflect the new way of working, not the old one.

Bringing It Together

None of these dynamics start the day a system goes live. They build on how much ownership and clarity people had going in, and they either ease or harden depending on what happens after the initial excitement of implementation fades. This is part of why Victoria Fide treats resistance management as a continuous thread through implementation rather than a single go-live event.

A Quick Gut-Check for Implementation Teams

• Have we given people a low-stakes way to practice before they’re expected to perform?
• Do frontline employees and managers have a real channel to flag confusion, and do we act on what we hear?
• Is our communication cadence fixed and ongoing, even when the project team is buried in troubleshooting?
• Are our leaders visibly using the new system themselves?
• Have performance metrics and incentives been updated to reflect the new way of working?
• Are we tracking sentiment and adoption, not just technical usage stats?

Resistance during an ERP implementation isn’t something you can afford to wait out. Left unaddressed, it hardens into permanent workarounds, shadow systems, and a workforce that’s just going through the motions instead of genuinely adopting the new way of working. If your organization is already navigating this, or wants to get ahead of it before your next go-live, Victoria Fide’s Change Management services are built to pinpoint exactly which dynamics are driving the pushback in your organization, whether that’s a competence gap, a communication breakdown, a leadership disconnect, or something else entirely, and to design the specific interventions that move your people from reluctant compliance to real ownership. The sooner resistance gets named and addressed, the sooner your implementation stops fighting friction and starts building the momentum it needs to succeed.