Mon – Sat: 9:00 AM – 7:00 PM IST
Implementation

ERP change management

The reason well-built systems get rejected — and what can be done about it before go-live rather than after.

In short

Change management in an ERP programme is the work of getting people to use the system as designed: involving them in design, communicating what changes and why, training on their actual processes, and supporting them through the first months. It is the difference between a system that works and a system that is used.

Why It Matters

Why this matters in practice

ERP failures are rarely technical. The system does what it was configured to do; people continue using spreadsheets alongside it, enter data late, or work around controls they do not understand. Every one of those is a change-management failure, and each is far cheaper to prevent before go-live than to correct afterwards.

Adoption, not functionality, is the usual failure mode
People resist controls they were not consulted about
Training on real processes beats training on screens
Workarounds are a signal, not a discipline problem
How It Works

How it works in practice

Involve users in design

The people doing the work know the exceptions. Excluding them guarantees a design that cannot handle real cases.

Explain the why

A control that seems like bureaucracy gets circumvented. The same control, explained, usually gets accepted.

Train on real processes

Train on the scenarios people actually face, with their data, not on a tour of the menu.

Identify local champions

One capable person per team answers more questions than a central helpdesk and is trusted more.

Measure adoption

Transactions entered on time, workarounds observed, support tickets by theme. Adoption is measurable.

Worked example

A worked example: the spreadsheet that would not die

Six months after go-live, a department is still maintaining the spreadsheet the ERP was meant to replace. The project team treats this as resistance and escalates.

Asking why produces a specific answer. The spreadsheet carries a column the ERP does not have — an informal priority flag the team uses to sequence work. Nobody mentioned it during discovery because nobody thought of it as data; it was just something they did. Without it, the ERP cannot support their actual workflow, so they use the ERP for the official record and the spreadsheet for the real one.

The fix is a custom field and a sort order, which is perhaps a day of work. The broader lesson is that shadow processes are diagnostic rather than defiant: they mark exactly the places where the system does not fit the work. A change programme that treats them as compliance failures loses the information. One that treats each as a question — what does this do that we do not — usually finds a small gap and closes it.

Key terms

The vocabulary, briefly

Term What it means
Sponsor The senior leader accountable for the change actually happening, not merely supportive of it.
Super-user A respected colleague in each department who learns the system deeply and helps others.
Resistance Opposition to the change. Usually rational, and usually information about something real.
Adoption Actual use of the new way of working, as distinct from the system being available.
Shadow process Spreadsheets and workarounds that survive alongside the new system.
What Goes Wrong

Common mistakes worth avoiding

Announcing rather than consulting

A system presented as finished invites resistance from people who were never asked.

Training weeks before go-live

Training too early is forgotten; too late is rushed. Close to go-live, then reinforced after.

Punishing workarounds

A workaround means the system does not fit the work. Investigate it rather than prohibit it.

Declaring success at go-live

Go-live is the start of adoption, not the end of the project.

What to measure

Numbers worth tracking

Metric What it tells you What distorts it
Transaction volume by module Whether the system is genuinely being used, by department.
Shadow processes identified Count them openly. A programme that finds none is not looking.
Support tickets by category Repeated questions indicate a training gap or a design problem, and the two need different responses.
Super-user engagement Whether departmental support is working or everything escalates to central IT.
FAQ

Questions we are asked about this

At discovery, not before go-live. The people who will use the system should be visible in the design phase, which is also when their knowledge is most valuable.
Spreadsheets maintained alongside the system, data entered in batches days late, and the same questions recurring months after training. All three are measurable signals.
At the point the decision is made, not when training is scheduled. People need to understand why the change is happening, what it means for their work, and what is expected of them, well before they are asked to attend a course. Programmes that begin communication a month before go-live spend that month managing anxiety that earlier conversation would have prevented.
By assuming it contains information. Someone objecting usually knows something about the work that the design missed, or has been through a previous implementation that went badly, or can see a consequence nobody else has. Listen specifically, separate the solvable from the merely uncomfortable, and fix what is solvable. Resistance treated as an attitude problem tends to go underground and re-emerge as shadow processes.
Choosing them for respect rather than availability, giving them genuinely deeper training than their colleagues, involving them during design and testing so they have ownership rather than instructions, and protecting some of their time for the role. A super-user who was volunteered because they had a light week will not carry their department, and everyone will know it.
Look at behaviour, not at sentiment. Are transactions actually happening in the system across all departments, or are some quiet? Are shadow processes shrinking? Are support tickets moving from 'how do I' towards genuine exceptions? Survey responses tend to measure how people feel about being asked, while transaction volumes measure what they actually do.
Related

Where to read next

ERP implementation phases

Read more

What is UAT?

Read more

Our ERP software solutions

Read more

Need this applied to your own systems?

We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.