To accept change is to choose the future
My experience in managing ERP projects has taught me that the major difficulty is not technical, but truly linked to the human element. Resistance to change is a constant, natural phenomenon. If it is not understood and managed, it can compromise any project, no matter how well-designed it is.
In this article, I analyze the different forms of resistance and the key stakeholders, including the project manager himself. Even though there are many things to experiment with in this area, I then propose a few strategies to transform reluctance into a driver of success.
The Many Faces of Resistance
Resistance is not a monolithic block. It manifests in different forms that must be identified to be addressed effectively.
- Emotional Resistance: This is the most visible and common type. It arises from fear, anxiety, or doubt. Users worry about losing their bearings or being unable to master the new system. Phrases like "We've always done it this way, why change?" or "I'll never manage it" are perfect examples.
- Cognitive Resistance: This is more rational and based on arguments, often partial. It translates into criticism of the software's features, cost, or presumed efficiency. "The new system isn't good enough" or "The return on investment will never materialize" are typical remarks of this type of resistance.
- Organizational Resistance: This is more insidious, as it results from the company's structure. Communication problems between departments, conflicts of interest, or a lack of leadership can create a force of inertia that slows down the project.
Stakeholders and Their Motivations
Each project stakeholder reacts differently because their interests and fears are distinct.
- End Users (Accountants, Management Controllers, Treasurers): They are the most directly impacted. Their resistance is often emotional, linked to fear of the unknown, loss of autonomy, or the feeling that their expertise is not valued. Yet, their commitment is essential to data quality and the project's success.
- Key Users: They are the project's ambassadors within their department, but can also be the most exhausted. Their resistance is often not linked to fear of change, but to work overload and fatigue. Juggling their daily duties with project meetings, testing, and training can lead them to doubt, lose enthusiasm, and ultimately slow down the project because they "can't see the finish line."
- Middle Management: Often caught between executive management and their teams, their resistance can be cognitive or tied to power dynamics. They fear losing influence due to greater information transparency.
- Your Own Project Team (Consultants, Developers): It's easy to forget that your allies can also resist. The introduction of new methodologies (like Agile), a planning change, or repeated travel can generate resistance due to loss of reference points, fatigue, or a feeling of lack of recognition.
- The Project Manager Themselves: You are the leader, but you are also human. You may yourself feel resistance to a team change or a schedule imposed by the client. These situations can lead to a feeling of loss of control, a questioning of your expertise, or simply exhaustion linked to accumulated stress.
Budget Reality, A Major Hurdle
Very often, activities related to change enablement are underestimated, or even absent from the initial budget. The client, who bears the responsibility for this adoption, does not allocate the necessary resources for communication, advanced training, or personalized support. Consequently, this workload, considered crucial but unfunded, falls onto the project manager's shoulders. They then become the unofficial manager of change management, by force of circumstance, a major risk that compromises the project's success.
Strategies for Turning Resistance into Satisfaction
Here are a few useful levers to transform a refusal into satisfaction.
- Communication as the Pillar: A lack of communication is the number one cause of failure. A project manager must be an outstanding communicator. Communicate early, often, and transparently. Organize workshops and demonstrations to involve users and reassure them.
- Involvement and Support for Key Users: Publicly acknowledge their effort. Try to alleviate their daily workload by requesting resources and ensure they feel valued. Maintaining their motivation is key to success.
- Adapted and Continuous Training: The fear of not knowing how is very real. Training must be progressive and personalized, with concrete case studies relevant to each person's daily work. Don't just settle for training before launch: post
- launch support is just as essential.
- Leadership by Example: Visible support from executive management is indispensable. The CFO (DAF) and CIO (DSI) must be project sponsors, actively participating in meetings and communicating about the expected benefits. Their commitment sets the example to follow.
- Self
- Management Actions: As a project manager, you must be the first to manage your own resistance.
Accept Change: Don't see it as a failure, but as a new playing field.
Communicate Openly: Talk to your team about your doubts; this will build trust.
Develop Your Resilience: Step back to better cope with the unexpected.
In conclusion, resistance to change is a factor that must be taken into account from the very beginning of the project. By adopting a human approach, communicating openly, and involving every stakeholder, we can transform fears into enthusiasm and resistance into a driving force for project success.