Change Management

Managing organisational change for ERP: best practices

How to manage ERP-driven change with practical sponsorship, training, adoption, and go-live support routines.

ERP projects fail less often because the software is wrong than because the organisation was not ready to work differently. Change management is not a communications side task; it is how the business reduces adoption risk and protects value.

For small and medium businesses, the challenge is often not apathy but overload. Teams are already busy, informal workarounds are deeply embedded, and leaders underestimate how much support people need once the new process is live.

Good change management turns the ERP programme from a system rollout into an operating change the business can absorb.

What good change management includes

• Clear sponsor messaging about why the change matters, what will improve, and what behaviours need to change.
• Role-based impact analysis so each team understands what is changing in their day-to-day work.
• Manager-led reinforcement before and after go-live, not just project-team communication.
• Training built around real tasks, real exceptions, and real decisions by role.

Best practices for lean organisations

• Start change work early, even if the project team is small.
• Equip frontline leaders to answer questions and coach new behaviours after consultants step away.
• Use a simple change network of respected team members instead of building a heavy formal structure.
• Measure adoption through transaction quality, exception volume, rework, and support dependency, not just attendance sheets.

Common failure patterns

• Senior leaders announce the project once, then disappear from visible sponsorship.
• Training is screen-based but not role-based, so people know where buttons are without understanding how to operate differently.
• Hypercare focuses on system defects while ignoring the human causes of repeated errors.
• Teams keep old spreadsheets and shadow processes alive because nobody has explicitly retired them.

What to do in the 30 days before go-live

• Confirm role-level readiness, not just project milestone completion.
• Rehearse the key daily and weekly operating routines with actual end users.
• Make support channels visible and name who is helping each function.
• Brief managers on the most likely points of confusion and the behaviours they need to reinforce.

FAQ

• Do smaller businesses really need change management? Yes. They often need a lighter model, but not no model.
• Who owns it? The project lead coordinates it, but managers and sponsors must actively carry it.
• What is the clearest sign it is working? Users adopt the new process consistently without recreating the old one in shadow tools.