Transformation and ERP “change fatigue” is real but it is not the whole story.
Over the years, I have heard the phrase “change fatigue” come up a lot in ERP and transformation programmes.
Teams feel stretched.
Engagement dips.
Resistance increases.
Momentum fades before go live.
Those challenges are genuine… whatever the ERP, whether D365, SAP, JDE, Infor, NetSuite, IFS etc… anyone who has worked on an ERP programme will recognise the challenges.
But here is the good news.
Change fatigue is not usually the reason ERP programmes fail. It is more often a signal that ownership and support need strengthening.
When organisations get that right, energy usually comes back.
This article covers
- Why ERP and transformation change feels hard
- What change fatigue looks like in transformation programmes
- Positive shift from fatigue to ownership
- What strong ERP and transformation programmes do differently
- Final thoughts on change fatigue
Why ERP, Transformation and Change can feel hard
Gartner HR research highlights a clear deterioration in how employees experience organisational change.
In 2016, the Gartner Workforce Change Survey found that 74 percent of employees were willing to change their work behaviours to support organisational change. By 2022, that figure had fallen to 38 percent.
At the same time, the volume of change has increased significantly. In 2022, the average employee experienced ten planned enterprise changes, such as restructures, culture initiatives or major technology replacements, up from just two in 2016, according to Gartner research.
| Year | Employee willingness to support change | Planned average enterprise changes per employee |
|---|---|---|
| 2016 | 74% | 2 |
| 2022 | 38% | 10 |
That does not mean people are anti change.
It means they have lived through:
- Too many initiatives layered on top of each other
- Change delivered to them rather than with them
- Big promises that did not always translate into day to day improvements
Against that backdrop, ERP programmes need to work harder, but they can still succeed.
What “Change Fatigue” actually looks like on ERP Programmes
In practice, it tends to appear as:
- Business subject matter experts disengaging part way through delivery
- Decision making drifting towards others
- Core team members juggling ERP work alongside full BAU roles
- Training overload close to go live
- A sense of “this is happening around us, not with us”
| Observed Behaviour | What It Often Signals | Why It Matters |
|---|---|---|
| SME disengagement mid-project | Loss of ownership | Design quality and adoption suffer |
| Decisions drifting away from SMEs | Confidence erosion | Accountability becomes unclear |
| ERP work alongside full BAU work | Capacity not protected | Burnout and delivery risk increase |
| Training overload near go-live phase | Late capability build | Retention and confidence drop |
| “Happening around us” sentiment | Low co-creation | Resistance hardens post go-live |
These are usually signals that ownership is not yet fully embedded.
The Positive Shift from Fatigue to Ownership
The most successful ERP programmes do not try to push through fatigue.
They reframe the problem.
Instead of asking
“How do we get people to accept this change?”
They ask
“How do we help people genuinely own it?”
That shift can change everything.
What strong ERP Programmes do differently
1. Ownership is visible and shared
Successful programmes make it clear that ERP is not an IT project. It is a business transformation.
Senior leaders do not just sponsor it. They actively shape it.
Ownership is visible and reflected in real decisions.
2. Change champions are created early
One of the most effective techniques is building a network of internal champions.
These are not just super users.
They are:
- Respected people from the business
- Involved early in design and testing
- Given a real voice in decisions
- Equipped to support colleagues locally
Champions turn change from something abstract into something human and trusted.
People typically listen to peers long before they listen to project plans.
3. People help build what they are expected to use
Co creation matters.
When end users are involved in:
- Process design
- UAT
- Real world scenario testing
Adoption stops feeling like compliance and starts feeling like pride.
Resistance often softens when people recognise their own impact on the solution.
4. Capability is built, not borrowed
The strongest programmes deliberately leave capability behind.
They invest in:
- Internal product owners
- Confident super users
- Clear post go live ownership
This reduces dependency on external partners and builds confidence across the organisation.
Ownership grows when people feel capable, not exposed.
5. Capacity is treated as a risk, not an afterthought
Where programmes really succeed, organisations are honest about workload.
They:
- Backfill critical roles
- Protect key people’s time
- Bring in targeted specialist support
Go Live is where ownership pays off
Go live is not the end of the journey.
It is where ownership really matters.
When issues arise, and they always do, the difference between success and struggle is ownership.
Programmes that invest in ownership and champions early cope better, adapt faster and recover confidence sooner.
Final thought on Change Fatigue
ERP change will always stretch organisations.
But fatigue is not inevitable.
When people:
- Understand the purpose
- Feel genuinely involved and part of the journey
- See leadership visibly owning the change
- Have champions they trust
Energy returns, resistance softens and adoption follows.
Ownership is crucial.
If you are thinking about a hire in transformation or ERP, or considering your next move, feel free to get in touch.
- Website: https://cedarstonerec.com/contact
- Email : peter@cedarstonerec.com
- Call : 020 4600 7766
