Why do ERP implementations fail or get delayed? Almost never because of the technology. It is usually due to misunderstandings, conflicts or resistance: the human factors.
Change management is the key to bridging the gap between technical implementation and successful use. This article highlights the crucial role of change management in ERP implementations. It explains which methods you – as a business or project manager – can use to guide your employees through the changes and how you can avoid typical pitfalls.
Definition: What is change management?
Change management is a structured approach to supporting change processes in organizations. It aims to promote acceptance of innovations, reduce resistance and successfully shape the transition to new ways of working. In the context of digitalization projects (such as the introduction of ERP), change management supports the smooth introduction of new technologies and processes.
What is the difference to project management?
Traditional project management focuses on planning resources, adhering to schedules and implementing technical aspects. In contrast, change management focuses on the human aspects of change: it empowers employees to accept and implement the changes. Both approaches complement each other and together contribute to the success of digitalization projects.
The four phases of change
People typically go through four emotional phases when changes are caused by external factors:
1. shock and rejection
In this first phase, those affected often react with surprise or rejection to the announced change. They tend to deny or underestimate the necessity of the change.
2. resistance and frustration
As soon as the reality of change sets in, fears and resistance can arise. Employees may feel overwhelmed and doubt their ability to deal with the change.
3. rational acceptance
In this phase, those affected begin to recognize the benefits of the change. They accept the necessity on a rational level, even if there are still emotional reservations.
4. commitment
In the final phase, employees integrate the change into their day-to-day work. They recognize the positive aspects and are actively committed to the new situation.
The role of change management
Change management supports this process by specifically addressing each phase. It prevents the people affected from getting “stuck” in one of the first phases. Through targeted measures, companies can accelerate the transition and increase acceptance of the change.
Why is change management so important when introducing ERP?
ERP implementation is an IT project, isn’t it? Of course it is. But not only. As mentioned at the beginning, human factors often have a greater influence on the course of the project. For the following reasons, change management is indispensable during ERP implementation:
Overcoming resistance to change
Challenge: ERP implementations often change established work processes, which can cause uncertainty among employees.
Solution: Recognize resistance at an early stage and reduce it through targeted communication and the involvement of those affected.
Promote user acceptance and adoption
Challenge: The success of an ERP system depends largely on how well it is accepted and used by users. If employees don’t like it or don’t get on with it, they will look for ways to avoid working with it.
Solution: Promote acceptance by explaining the advantages of the new system and supporting employees during the familiarization phase.
Find out more: What you can do if there is resistance to the ERP system
Minimize productivity losses during the changeover
Challenge: The introduction of a new ERP system can initially lead to a loss of productivity. The users do not yet have a routine and may take longer to complete their tasks.
Solution: Shorten this phase through targeted training and support measures and restore efficiency more quickly.
Adapting corporate culture to new ways of working
Challenge: A new ERP system often requires fundamental changes in the way employees think and work. Existing corporate cultures can inhibit this change.
Solution: Support in establishing new ways of thinking and work processes and integrating them into the existing culture. This concerns, for example, cross-departmental collaboration, data-supported decision-making and a stronger process orientation.
Maximize ROI through effective use of the ERP system
Challenge: An ERP system can only develop its full potential if it is used effectively by everyone involved. For example, data analyses will not produce accurate results if the data is incompletely maintained or outdated.
Solution: Ensure that employees understand the new opportunities and can make the best possible use of them – above all, that they understand how they personally benefit from them.
Also interesting: How much change is allowed during ERP implementation?
Success factors for ERP change management
What makes for successful change management? Pay attention to the following factors when planning the ERP implementation:
Clear communication and transparency
Inform your employees early and regularly about the progress of the ERP implementation. Explain the reasons for the change and the expected benefits. Use various communication channels such as meetings, newsletters or a dedicated project website.
Be open to questions and concerns and address them promptly. Transparent communication builds trust and reduces uncertainty.
Defined processes and roles, change agents
Clearly define who takes on which tasks and responsibilities in the change process. Define clear decision-making paths.
Appoint change managers (or change agents) in each department who can act as contact persons and identify problems at an early stage – these are often also the key users. Provide these people with the necessary skills, resources and authority. Train them not only in the ERP system, but also in change management methods.
Involvement and training of employees
Actively involve your employees in the change process. Ask for their ideas and concerns and take them into account during the course of the project.
Provide comprehensive training that not only covers the technical aspects of the ERP system, but also explains the new business processes. Provide learning materials in different formats to support different types of learners. Schedule regular refresher courses even after implementation.
Leadership and support from management
Management should act as a role model and actively drive the change. Have managers communicate regularly about the importance and progress of the ERP project.
Make sure that you use the new system yourself and demonstrate its benefits. Encourage managers to be open to feedback and to respond flexibly and empathetically to challenges.
Continuous feedback and adjustments
Establish feedback mechanisms to obtain regular feedback from users. These can be short surveys, feedback rounds in meetings or a digital suggestion system. Analyze the feedback carefully and derive specific improvement measures from it.
Communicate transparently which adjustments have been made based on the feedback. This way, everyone can see that it is worth getting actively involved.
Consider cultural aspects
Analyze the existing corporate culture and identify potential conflicts with the new ways of working. Develop strategies to carefully evolve the corporate culture towards the new requirements.
Promote an open error culture in which problems are seen as opportunities for improvement. Create spaces for informal exchanges about the changes in order to support emotional processing.
Creative tool: the headstand method
The headstand method is a creative tool in change management that helps to look at problems from an unusual perspective. Instead of asking how a project can be successfully implemented, the question is turned around: “What do we have to do to guarantee that the project will fail?“
This provocative approach often reveals surprising insights. It makes hidden risks visible and uncovers blind spots. After the brainstorming session, the collected “failure factors” are transformed into positive recommendations for action. This creates a valuable guide for the project. The method is particularly suitable for kick-off meetings or when a project is stalling.
Guidelines for change management in digitalization projects
Even though change management is always individual, projects always follow the following phases. The following section shows how to apply the success factors described above in specific measures during the course of the ERP implementation.
Preparation phase: analysis of the current situation and definition of objectives
Start with a thorough analysis of the current situation in your company. Identify the areas that will be affected by the ERP implementation and define clear, measurable goals for the project. Develop an understanding of the corporate culture and possible resistance to change.
Planning phase: Stakeholder analysis and strategy development
Carry out a detailed stakeholder analysis to identify all relevant interest groups. Develop your change management strategy based on this analysis.
Plan specific measures for communicating, training and supporting employees. Set milestones and define success indicators for change management.
Implementation phase: communication, training and support
Implement your planned measures. Communicate regularly and transparently about the progress of the project. Carry out training courses to prepare employees for the new system. Provide
Stabilization phase: progress monitoring and adjustments
After the ERP implementation, closely monitor how employees are using the new system. Collect continuous feedback and identify areas where support is still needed. If necessary, conduct follow-up training or adapt processes.
Evaluation phase: Measuring success and lessons learned
Evaluate the success of your change management process using the previously defined indicators. Conduct interviews or surveys to measure employee satisfaction and acceptance. Document the findings for future projects. Celebrate successes and acknowledge the contribution of everyone involved to the success of the project.
Measuring the success of change management
Is your change management project successful? You should not just assess this based on gut feeling, but systematically measure it. In this way, you can prove the value contribution of change management and optimize future initiatives.
Quantitative indicators of success
Quantitative indicators provide measurable data to evaluate change management success. Consider the following key figures:
- System utilization rate
- Number of support requests
- Productivity development after the ERP implementation
- Participation rates in training courses
- Results of knowledge tests
- Error rates during system operation
- Throughput times of business processes
Qualitative indicators of success
Qualitative indicators capture the softer but equally important aspects of change management. Consider the following aspects:
- Employee satisfaction with the new system
- Acceptance of the change process
- Quality of interdepartmental cooperation
- Changes in the corporate culture
- Employee commitment and motivation
- Quality of communication in the project
- Perception of management support
Gather this information through employee surveys, focus groups or individual interviews.
Long-term vs. short-term performance measurement
Distinguish between short-term and long-term success indicators.
Short-term indicators:
- Initial acceptance rate
- Training participation and success
- First changes in productivity
- Number of change agent activities
Long-term indicators:
- Sustainable increase in productivity
- Improvement of business processes
- Realization of the planned project goals
- Development of employee satisfaction over time
- Adaptability to future changes
Establish a continuous monitoring system to take both perspectives into account and ensure the long-term success of your ERP implementation.
Common pitfalls during ERP implementation
Do not fall into the trap of making the following common mistakes. Use the measures described above to avoid the negative consequences.
Ignoring employees’ fears
Do not underestimate the emotional reactions of your employees to the impending change. They may be afraid that they will be overwhelmed by the new system or that their job will be “rationalized away”. Ignored fears can lead to active or passive resistance and jeopardize the success of the project.
Lack of support from top management
Without visible, continuous support from management, an ERP project quickly loses priority and credibility. Employees will notice if management is not fully behind the project. They may then become demotivated and only implement the project half-heartedly. A lack of leadership can also delay decisions and lead to conflicts between stakeholders.
Read also: The guide for project management during ERP implementation
Underestimating complexity and required resources
ERP implementations are often more complex and resource-intensive than initially assumed. The consequences? Overworked employees, missed deadlines and budget overruns. Time pressure can lead to the wrong decisions being made and quality being neglected during implementation. Too little time for training and induction can also take its toll because employees feel left alone and overwhelmed.
Neglecting process optimization
It does not make sense to simply transfer your old business processes to the (new) ERP system. Why? Firstly, employees will then hardly recognize the benefits of the new ERP system; why should they use it? Secondly, there is a risk that the potential of the ERP system will not be fully exploited and the investment will not be worthwhile.
However, changes to core processes demand a lot from employees: they have to get used to new routines. The temptation to leave everything as it is may therefore be great. Instead, you should consider process optimization as an important part of the ERP implementation and support it with change measures.
Unbalanced project management
For a successful project, you must manage to keep the “magic triangle” of requirements, budget and time in balance. Excessive time pressure impairs the results and overwhelms those involved. Too tight a budget can prevent important adjustments, while too many requirements can overload and delay the project. When many stakeholders are involved, it takes a lot of empathy and negotiation skills to avoid such imbalances.
Conclusion: People are the key to success
Despite the technical complexity of an ERP implementation, we must not forget one thing: In the end, the human factor determines the success or failure of the project. Even the most sophisticated software is ineffective if employees do not accept it and use it effectively.
Effective change management ensures that the people in the company understand, support and actively shape the change. You should therefore invest at least as much energy in supporting your employees as you do in the technical aspects. Only when the people are “on board” can your ERP system develop its full potential – and only then will you achieve your strategic goals.
