Change Management
Change management is the systematic effort to guide the affected people and processes through profound change – in an ERP implementation, all the measures that ensure employees accept, understand and productively use the new workflows and the new system.
Change management is the systematic, planned steering and guiding of change within an organization – with the goal that the people affected accept and support the transition. In the context of an ERP implementation, change management covers all the measures beyond technology and configuration that ensure employees understand the new processes, master the new software and adapt their familiar ways of working to the new system. It addresses the "soft" side of a project: communication, involvement, training, motivation and dealing with resistance.
At its core, change management rests on the insight that even a perfectly configured ERP system fails if users are unwilling or unable to use it. Technology can be planned and tested; behavior and acceptance can only be guided. Change management closes this gap by leading the organization through the transition in a structured way – from the first announcement through go-live and into stable regular operation – and by turning those affected into participants early on.
At a glance
- Guides people and processes through change – the "soft" side of an ERP project
- Goal: acceptance, competence and productive use of the new system
- Building blocks: communication, involvement, training, resistance management
- Key users play a central role as multipliers between the project and the departments
- Not to be confused with IT change management (change control under ITIL)
What does change management include?
Change management is not a single tool but a bundle of coordinated building blocks. It starts with analysis: who is affected by the change, which workflows will change, and where can resistance or fears be expected? On this basis, a change concept is developed with clear goals, responsibilities and a timeline aligned to the project roadmap.
The operational building blocks are above all communication, involvement and enablement. Communication means explaining the change early, honestly and repeatedly – why the company is switching, what changes for each individual and what benefits it brings. Involvement means engaging the affected departments in designing the new processes rather than presenting them with a finished solution. Enablement, finally, covers training, practice environments and support so that users can operate the new system confidently.
The role of key users
A central element in the change management of an ERP implementation are key users: experienced employees from the departments who accompany the project closely, help shape the new processes and carry their knowledge into their teams. They act as multipliers and translators between the project team and the workforce – they know the daily practice, test the system from a user perspective and, after go-live, are the first point of contact on site. Well-chosen key users who are taken seriously are one of the strongest levers for acceptance.
How does change management work?
In practice, change management usually follows a phase model. Well known is the three-step "unfreeze – change – refreeze" by Kurt Lewin: first the readiness for change is created (unfreeze), then new processes are introduced and practiced (change), and finally the new ways of working are anchored and stabilized in everyday life (refreeze). Other models such as Kotter's eight-step model or the ADKAR model set similar priorities but place stronger emphasis on leadership, urgency and the individual change curve.
In practical terms this means: before the project, a sense of necessity is created and a clear vision communicated. During the project, users are involved, trained and kept informed about progress. Around go-live, intensive support – such as a hypercare phase – ensures that initial friction does not turn into frustration. Afterwards, successes are made visible and the new workflows become second nature, so that no one falls back into old patterns.
Dealing with resistance
Resistance is normal in far-reaching change and is not a sign of ill will. It arises from uncertainty, extra effort during the transition phase or fears about one's own job. Effective change management takes resistance seriously, makes its causes visible and meets it with transparency, involvement and quick small wins. If concerns are ignored, they later manifest as sluggish adoption, workaround solutions or poor data quality in the new system.
Why change management matters in an ERP implementation
The value of change management shows directly in project success. Studies on IT and ERP projects attribute delays and failures far more often to organizational and human factors than to technical ones. A system that the workforce rejects gets bypassed, maintained half-heartedly or used only superficially – and then delivers neither clean data nor the hoped-for efficiency gains. Change management reduces exactly this risk.
Concretely, good change support shortens the time to productive use, reduces support effort and input errors after go-live, and safeguards data quality because users understand the new processes and carry them out correctly. Economically, change management is therefore not a "nice to have" but the lever that makes the investment in an ERP system take effect at all. Anyone who pays only for the software but does not bring the people along risks squandering the benefit of the implementation.
Change management in the ERP project
In an ERP project, change management runs in parallel with the technical project track and is closely interwoven with it. As early as the ERP selection and the capture of requirements in the requirements and functional specifications, it is decided how much the processes will change – and thus how much change support is needed. During the implementation, key users are involved, training is scheduled and communication is tied to the project milestones.
Around go-live, change management has its greatest effect: users must be trained and prepared, points of contact must be available, and the hypercare phase must be closely supported. The transition into stable regular operation – the actual onboarding of the organization onto the new workflows – is only complete once the new processes run routinely and without constant questions. Change management therefore does not end with the technical go-live but only with lived acceptance.
Distinction: change management vs. project management and IT change management
Change management is often confused with project management but complements it. Project management steers the scope, schedule, budget and resources of an undertaking – it makes sure the system is finished on time and within budget. Change management makes sure the organization actually accepts and uses this result. Both run in parallel: a perfectly managed project can still fail if no one has guided the people through the change.
Equally important is the distinction from IT change management: in IT operations (for example under the ITIL framework), this term means the controlled steering of technical changes to existing systems – that is, the orderly requesting, assessing, approving and documenting of updates, configuration or software changes during ongoing operation. Organizational change management, by contrast, targets people and behavior. Both share the name but pursue different goals.
Example
Case study: a mid-sized company brings its workforce along in the ERP switch
A retail company with around 80 employees replaces its patchwork of legacy tools with a modern ERP. Instead of introducing the software quietly in the background, management names a key user from each department early on, explains the goal and benefit of the switch at a staff meeting, and sets up a regular project newsletter. The key users test the system, report back practical adjustments and then train their colleagues in small groups.
When the warehouse initially worries that the new picking process is more complicated, change management kicks in: the responsible key user gathers the criticism, the project team simplifies two screens, and the success is communicated visibly. After go-live, a four-week hypercare phase with a daily help desk supports the start. The result: the workforce uses the system actively from the outset, data quality stays high and support effort drops faster than expected.
Frequently asked questions
Matching ERP systems
Related services
Questions about Change Management in your ERP project?
We advise vendor-neutrally – and implement it ourselves on request.