Posted under: Change Management Strategy | ~9 min read
Your ERP vendor has a project plan. It has go-live dates, data migration milestones, integration timelines, and UAT checkpoints. It probably runs to several hundred rows in Microsoft Project.
Here's what it doesn't have: a plan for the people.
Not because your vendor doesn't care. Because that's not what they sell. They sell the system. The change management — the part that determines whether anyone actually uses the system — is almost always underfunded, underestimated, or assumed to happen on its own.
This post is the people plan your vendor won't give you. It covers what change management in ERP implementations actually looks like, why it fails so often, and what you need in place before your go-live date to avoid becoming another failed implementation statistic.
Why ERP Implementations Fail (It's Not the Software)
The Standish Group's CHAOS report has been tracking software project outcomes for decades. The numbers are uncomfortable: somewhere between 50% and 70% of large ERP implementations fail to meet their original objectives — on time, on budget, or in terms of actual adoption.
When you dig into the post-mortems, the technical failures are the minority. The common threads are:
- User resistance that wasn't anticipated or managed
- Training that happened too late and covered the wrong things
- Stakeholder alignment that looked solid until go-live pressure exposed the fault lines
- Middle management that never bought in and quietly undermined adoption
- No plan for Day 91 — what happens after go-live when the vendor leaves and the hypercare period ends
These aren't technical problems. They're people problems. And they're almost entirely predictable — if you're looking for them early enough.
The Structural Problem with Vendor-Led Change Management
ERP vendors — even the good ones — have a fundamental conflict of interest when it comes to change management. Their contract ends at go-live (or shortly after). Their success metric is the system being live and technically functional.
What happens to the people using that system over the next 18 months is, technically, your problem.
This isn't cynicism. Most ERP vendors are staffed with brilliant technical people. Change management specialists are not their core competency, and they're not trying to pretend otherwise. The good ones will tell you straight: "You need a change management partner. We'll handle the system."
The problem is that too many organizations hear "change management" in the proposal and interpret it as "training." Then they fund a few days of end-user training, call it done, and wonder why adoption is at 40% six months later.
What Actual ERP Change Management Looks Like
A real change management program for an ERP implementation runs in parallel with the technical workstream from Day 1. Not from three months before go-live. From Day 1.
Here's what it includes:
Phase 1: Foundation (Months 1–3)
Stakeholder mapping — Who is affected by this implementation, and how? This isn't just the end users. It's the middle managers whose reporting changes. The finance team whose month-end close process is about to be redesigned. The IT team who will own support post-hypercare. The executives who approved the budget and will be asked whether it was worth it.
Map influence, not just impact. Some people who are mildly affected have outsized influence over whether others adopt.
Resistance anticipation — Before a single user touches the system, identify where resistance will come from. Every ERP implementation has predictable flashpoints: the power user who built the old workarounds and is now watching them get replaced, the department that's being asked to change the most, the region that had the least input into the selection decision.
Name the resistance early. It doesn't go away by pretending it isn't there.
Sponsor alignment — Your executive sponsor needs to do more than approve the budget. They need to be visibly, verbally committed to this change — not once at kickoff, but consistently, throughout the project. If your sponsor goes quiet when the going gets hard (and it will), adoption will follow their signal.
This is usually where vendor-led implementations are weakest. Getting a signature is not the same as building a sponsor.
Phase 2: Build (Months 3–6)
Communications planning — Your users should never be surprised by what this system is going to require of them. A structured communications plan maps what messages go to which stakeholders, at what stages, through what channels, and from whom.
"From whom" matters more than people expect. A message from a peer change champion lands differently than the same message from IT. A message from a respected department head lands differently than one from the project team. Plan the messenger, not just the message.
Training strategy (not just training) — Training that happens once, three weeks before go-live, for a system that changes how people do their jobs every day, is not sufficient. It's better than nothing, but not by much.
Effective ERP training strategy includes:
- Role-based training (not one generic course for everyone)
- Timing aligned to when people will actually use the functionality (not too early)
- Reinforcement mechanisms after go-live — job aids, super users, support channels
- Leadership-specific training on dashboards and reporting, separate from end-user training
Change champion network — Identify and activate 2–3 change champions per department. These are credible, respected peers who can answer "how does this affect my workflow" questions in real language, not system administrator language. They're your on-the-ground adoption accelerators, and they cost you almost nothing to activate — as long as you activate them early enough.
Phase 3: Go-Live and Beyond (Month 6+)
Hypercare with a handoff plan — Most implementations have a hypercare period — extra support in the first 30–60 days after go-live. This is good. The mistake is not having a plan for what happens when hypercare ends.
Who owns tier-1 support after the vendor leaves? Who monitors adoption metrics? Who escalates when a team is struggling? If you don't have answers to these questions before go-live, you'll be scrambling to find them at exactly the worst moment.
30/60/90 day adoption tracking — Go-live is not done. Go-live is the beginning of the hardest part. The first three months post-go-live are when most ERP implementations quietly lose adoption — people find workarounds, old habits reassert themselves, the system gets used for some things but not others.
Formal adoption tracking in this window — measuring not just system usage but behavioral adoption — is the difference between an implementation that sticks and one that becomes a very expensive spreadsheet workaround.
Sustainability check-ins — At 90 days post-go-live, run a structured sustainability check: Are the expected behaviors in place? Where are the gaps? What reinforcement is needed? This is the conversation your vendor won't initiate because their contract is already closed.
The Budget Question
Most ERP implementations allocate 10–15% of the technical project budget to change management, if they allocate anything at all. Best practice research (Prosci, McKinsey, others) consistently puts the optimal range at 15–20% of total implementation cost.
For a $2M ERP implementation, that's $300K–$400K in change management investment.
The math works. ERP implementations with excellent change management are 6x more likely to meet or exceed project objectives than those with poor or no change management. If your implementation has a 40% chance of meeting its objectives without change management investment, and a proper change program doubles that, you just justified the investment many times over.
More practically: the average cost of a failed ERP implementation — in lost productivity, rework, delayed go-live, and leadership credibility — far exceeds what structured change management would have cost.
Building the People Plan: Where to Start
If you're already in an ERP implementation and reading this thinking "we're three months from go-live and none of this has happened" — don't panic. You can't run a full program in three months, but you can run a targeted one.
Prioritize in this order:
- Stakeholder map with resistance signals — one week, if you move fast
- Sponsor activation — get explicit commitments on visible behavior, not just budget approval
- Change champion identification and briefing — even informal champions help
- Targeted communications — at minimum, no surprises at go-live
- Role-based training with post-go-live job aids — not just a training day
- Adoption tracking plan — even a simple one is better than none
If you have more runway, build backwards from go-live and fill in Phase 1 and 2 activities as time allows.
What AlignHQ Was Built For
AlignHQ is purpose-built for exactly this kind of work. Stakeholder mapping, readiness assessments, risk registers connected to your comms plan, training trackers, and post-go-live adoption tracking — all in one place, all connected.
For ERP implementations specifically, the ability to track adoption past go-live is the feature most practitioners tell us they couldn't find anywhere else.
Start a free trial. No credit card required. Set up your ERP initiative in AlignHQ in under 10 minutes and see what it looks like when the people plan lives in the same place as everything else.
AlignHQ supports change management for ERP implementations, digital transformations, and organizational redesigns. Built for practitioners who manage the people side of change.
Ready to build your change management foundation?
AlignHQ gives your team the structure to do change management right — stakeholder maps, readiness assessments, comms plans, and risk registers in one place.
Start Free Trial →