Change management
Change management is the structured approach to transitioning individuals, teams, and organisations from their current state to a desired future state enabled by ERP. While technical implementation focuses on software, change management addresses the human side – ensuring users adopt new processes and systems. Studies show that projects with excellent change management are six times more likely to meet objectives.
1. Why change management matters
ERP implementations change how people work. Without effective change management:
- Users resist, revert to old ways (shadow systems).
- Productivity dips longer than necessary.
- Expected benefits (ROI) are not realised.
- Key talent may leave.
2. ADKAR model
The ADKAR model by Prosci is a popular framework for individual change:
| Element | Description |
|---|---|
| A Awareness | Understanding why change is needed (the business case). |
| D Desire | Motivation to participate and support the change. |
| K Knowledge | Training and information on how to change. |
| A Ability | Implementation of new skills and behaviours. |
| R Reinforcement | Sustaining the change (coaching, rewards). |
3. Stakeholder analysis
Identify and map stakeholders by influence and impact:
- Champions: High influence, positive – engage as advocates.
- Resistors: High influence, negative – address concerns early.
- Observers: Low influence – keep informed.
A stakeholder engagement plan defines how to communicate and involve each group.
4. Communication planning
Effective communication answers: "What's in it for me?" (WIIFM). Plan includes:
- Key messages: Why ERP? How will it help individuals?
- Channels: Town halls, emails, intranet, posters, team meetings.
- Frequency: Regular updates – don't let rumours fill the void.
- Two‑way feedback: Surveys, Q&A sessions, focus groups.
5. Training & competency
Training ensures users have knowledge (ADKAR's K) and ability (A). Key elements:
- Role‑based curricula: Different training for finance, warehouse, sales.
- Methods: Classroom, e‑learning, simulations, cheat sheets.
- Train‑the‑trainer: Empower super‑users to support peers.
- Just‑in‑time: Training close to go‑live, not months before.
6. Overcoming resistance
Resistance is natural. Common reasons and responses:
| Reason | Approach |
|---|---|
| Fear of job loss | Explain how roles will evolve, not disappear. |
| Loss of control | Involve users in design and testing. |
| More work during transition | Acknowledge, provide support, celebrate quick wins. |
| Past negative experiences | Listen, demonstrate improvements, pilot with champions. |
7. Organisational culture
Culture eats strategy for breakfast. Assess cultural readiness:
- Hierarchical vs collaborative: How are decisions made?
- Risk tolerance: How comfortable with change?
- Past change history: Were previous changes successful?
Tailor change approach to cultural context.
8. Sustaining the change
Change doesn't end at go‑live. Reinforcement activities:
- Hypercare support: Immediate post‑go‑live assistance.
- Performance dashboards: Show progress and benefits.
- Celebrate wins: Recognise teams and individuals.
- Continuous improvement: Gather feedback and optimise.
Key Takeaways
- Change management addresses the human side of ERP – critical for adoption and ROI.
- ADKAR model provides a framework for individual change.
- Stakeholder analysis, communication, and training are core activities.
- Resistance is normal – address concerns with empathy and evidence.
- Change must be reinforced after go‑live to sustain benefits.
When should change management start? At project initiation – ideally during selection phase. Early engagement builds buy‑in.
Who is responsible for change management? Ultimately the project sponsor and leadership team. A dedicated change manager leads the work.
What is a change network? A group of influential employees from across the organisation who act as change champions and provide feedback.
Continue Reading in ERPEDIA
For structured, vendor‑neutral ERP advisory → Speak with an independent ERP advisor.