The ERP goes live on a Monday. By the start of the following week, the plant scheduler is back to using her old reliable spreadsheet.
Not because the new system is broken. It does everything the demo promised. Work orders, inventory, production schedule — all in one place now, exactly as the project team drew it on the whiteboard 18 months ago. She just doesn't trust it yet, and she has a shift to run. There isn't any time to experiment.
So she double-clicks to open her spreadsheet, hidden in a vaguely named folder on her desktop. Just to be safe. Down the line, a shift supervisor does the same, rekeying numbers into the workbook he's maintained for a decade because that's the version he knows he can defend in the morning huddle. A buyer keeps a paper log.
None of them are trying to be difficult or resistant. They're experts at what they do, suddenly made slower and less sure of themselves, protecting the operation (and their jobs) the only way they know how.
Three months in, leadership pulls adoption numbers and finds half the plant quietly running a shadow system. No one has rebelled. No one has skipped a training. The rollout went exactly to plan. The workers on the plant floor have simply decided the promises of "efficiencies" and "synergies" down the road aren't enough to justify a slowdown today.
It's tempting to read a story like that as a one-off or as a uniquely manufacturing problem. It's neither. Swap the plant floor for a health system's finance office, a university's procurement team, a utility's field operations, a logistics provider's dispatch center, or the back office of a company three months into a private equity carve out, and the story barely changes.
The system works. Yet the people don't change.
Change management is the capability that determines whether your ERP pays off
ERP change management is the single most reliable predictor of whether an ERP program will deliver what it set out to achieve by getting an organization to let go of the way it has always run and embrace a new, more efficient way. Change management for ERP is not the cookie cutter communications and training that most people associate it with. It must focus on stakeholder management and process education, key differentiators in determining the success of your program.
Prosci’s research found that projects with excellent change management are seven times more likely to succeed.
Another study looked at what separates successful ERP outcomes from failed ones after go-live and found that organizational factors (the people side of things) far outweigh technological ones.
Broader studies of ERP failure consistently surface the same drivers: a lack of leadership involvement, end-user resistance, and processes that were never redesigned to fit the new system. Every one of those pain points can be mitigated with an intentional, strategic change management program.
Which is why it is so strange that most programs treat change management as an afterthought. It's the variable most tied to success, and yet it’s also the first line item cut when budgets tighten.
But ERP change management is the organizational capability that decides whether your tech investment ever converts to value.
Some sectors carry more industry-specific nuances that complicate adoption than others, though none are immune. Manufacturers, in particular, wrestle with legacy systems bolted together over decades and shop-floor processes that don't easily meld with new software.
The complexity that defines the organization is the same complexity that strains its ERP program.
When failure doesn’t look like failure: The risk of a successful technology implementation without change management
When the system doesn’t crash, and it goes live roughly on time and on budget, it’s hard to call that a failure. There’s no post mortem for a program that technically succeeded.
And therein lies the risk.
It shows up in the small operational tells. Like the maintenance planner who keeps scheduling with a whiteboard because the new work order module takes eleven clicks to do what a grease pencil can do in one stroke.
The dispatch team that runs the day off a shared spreadsheet because the new transportation module doesn't reflect how loads actually get built and routed.
None of it registers as a crisis. All of it registers as friction, and friction gets engineered around fast. The symptoms differ by setting: throughput softens and overtime creeps up in a plant; the monthly close slips in a finance office; error rates and rework climb in a service center; grant reporting falls behind on a campus. Different dashboards, same story.
What does sustainable ERP user adoption require?
Here's the good news in each of those vignettes. The scheduler, the planner, the administrator, the field supervisor, and the controller can change if presented and supported in the right way. Every workaround they build is a reasonable response to a system they weren’t prepared to put their trust in. Close that gap (or ideally, avoid creating it in the first place) and they’ll adapt quickly.
Most organizations never educate their people on how the work itself is changing because they focus almost exclusively on educating them on the system they'll use to do it.
System training teaches a buyer how to navigate the new procurement module; it’s often boiled down to a day of instruction three weeks before go live to teach people essentially which buttons to press. Process education teaches that same buyer why the workflow was redesigned in the first place plus what problem it's solving, where their role fits, and how their piece connects to everyone else's.
Take three-way match. Many manufacturers go straight from purchase order to payment; someone buys it and someone pays for it. No purchase requisition to start off with. When an ERP introduces a formal PR step, it's not bureaucracy for its own sake. It's what allows procurement to consolidate buying, negotiate better pricing, and ensure that accounts payable can match the receipt to the PO before a vendor gets paid. It keeps inventory accurate. It protects margins. It affects the plant floor downstream.
But if the person now responsible for logging receipts only learns how to enter them in the system, and not why that step exists and what breaks when it's skipped, they'll find a faster workaround. Usually a spreadsheet.
That's what process education is. And without it, even a technically clean ERP rollout quietly degrades into shadow systems and bad data.
This is the part that gets compressed when a timeline slips or a budget tightens. If an organization invests in training at all, it’s usually on the system alone. The deeper adoption work (process education, role clarity, leadership alignment, readiness) gets trimmed to a line item at best, then to a footnote, then to an assumption that people will "figure it out." But they don’t.
There's a bigger shift hiding in that framing. Most organizations still build change management around a single milestone — the go-live date. But go-live is rarely the last major change that organization will face. The alignment work, the change-agent networks, the readiness assessments, the ongoing optimization. Companies rebuild all of it from scratch for each next initiative, but the organizations that pull ahead are building a durable capacity for continuous change that gets cheaper and faster to deploy every time it's used, whether the next test is an AI rollout, an integration, or a policy shift.
ERP change management in three phases
Real, sustainable ERP change management is built earlier and runs deeper. It requires 14 key elements across three phases to enable adoption and sustainability of the future state.