Every day, hundreds of software implementation projects launch around the world. Each one represents a business’s hope for order, transparency, and increased efficiency. But the statistics are relentless: a significant portion of these projects either fail outright or exceed their budget and timeline.
Why does this happen? Formally, the blame is placed on complex software, poorly written technical specifications, incompetent developers, or planning errors. However, practical experience shows that the real reasons lie on an entirely different plane. They are connected to the people who will work with the new system and the atmosphere within the company. It is these “hidden adversaries”—the users and their managers—who most often decide a project’s fate.
What is an Implementation Project, Really?
Implementing software (whether it’s an ERP, CRM, ATS, or an industry-specific solution) is not just installing a program on computers. It is a transformation of business processes and, more importantly, a shift in the employees’ mindset.
The classic stages look like this:
- Discovery and Analysis: Understanding how the company currently operates.
- Technical Specification: Documenting the desired future state.
- Development and Configuration: Adapting the system to the business’s needs.
- Testing: Verifying that everything works correctly.
- Pilot Launch and Training: The most painful stage, where theory meets reality.
- Go-Live: Launching the system for the entire company.
Modern flexible methodologies (like Agile) emphasize constant feedback from the client to mitigate risks. But even they are powerless against the main challenge: human resistance. The unwillingness to change, fear of the new, and the habit of working “the old way” can kill any project, no matter how technically perfect.
The Role of Leadership: Myths and Reality
Every project management textbook states: “The critical success factor is support from top management.” It’s believed that if the CEO is on board and issues the right orders, everything will go smoothly.
In practice, support from above alone is not enough. A business is a living organism with its own hierarchy and interests. The influence of different employee groups on a project varies greatly. The most dangerous adversary is not where one is used to looking.
Level 1: Leadership (Top Management and Owners)
For them, the system is a management tool. They need transparency, fast reporting, and reliable data. Top management is the project’s main sponsor: they allocate the budget and expect results.
Problems with this level are rare. The only real risk is if a leader loses interest halfway through, shifting focus to new priorities. But overall, this is the most loyal and invested participant in the process.
Level 2: Doers (Rank-and-File Employees)
From a hierarchical standpoint, this is the level opposite leadership. These are the people who will work in the system daily, entering data and “pressing the buttons.” Their position is simple and humanly understandable: “We’re used to working the old way; no one taught us this new system; we don’t need it.”
Resistance from doers can be overt: complaints about the interface’s complexity, nostalgia for “good old Excel,” and outright sabotage of data entry. But this group is the easiest to work with. Their motivation lies in the practical. If they can clearly see that the program relieves them of routine tasks (automatically filling out documents, eliminating double entries), the resistance melts away. Doers quickly become allies if the change makes their lives easier.
Level 3: Middle Management — The Hidden Threat
Paradoxically, it is middle management that most often becomes the main protagonist on the “hidden front” and the most problematic link.
In an ideal world, department heads immediately embrace the change, understand the logic of the new system, and are ready to work in new ways. They become guides and controllers for their subordinates. In practice, however, it’s different.
Resistance from middle management usually comes in two forms.
1. Conscious Resistance / Political Games
Some managers understand that the new system threatens their informal power. Previously, they were the sole owners of information; they could polish a report or hide their department’s shortcomings from leadership. A transparent system strips them of this privilege—the director can now see the real picture without it being filtered through the manager’s interpretation.
These managers will look for thousands of shortcomings, bombard the vendor with requests for hundreds of “critical” improvements (often contradicting each other), thereby implicitly sabotaging the project. They are the most dangerous opponents, but they can be identified. And they can be dealt with—firmly, using administrative authority. A clear signal from leadership: “The shadow game is over; this system will be implemented at any cost”—often forces these “political players” into, if not agreement, then coerced compliance.
2. Functional Powerlessness / Inability to Change
The second group consists of people who grew up within the old processes. They might be decent specialists within that outdated paradigm, but they are incapable of grasping the logic of the new system. They lack the qualifications, mental flexibility, or desire to learn. They aren’t consciously lying; they genuinely believe the system is “stupid” and “doesn’t account for our specifics” because they themselves cannot articulate those specifics in the terms of the new program.
Working with such people is nearly impossible. They will slow down the project, generate endless “improvements” (leading to dead ends), and demoralize their subordinates and the project team with their pessimism. Implementation requires a manager to be adaptable. If a person is not ready for this, they become a ticking time bomb for the entire project.
Factors for Success: How to Turn Enemies into Allies
The success of an implementation depends less on the chosen solution or budget size and more on properly managing the key players on the client’s side. Here are three main rules:
- Top-down support is like air. Without it, the project suffocates instantly. But support alone is not enough. Leadership must actively engage with middle management, communicating the inevitability of change and each person’s individual responsibility.
- Rank-and-file employees are your allies. Show them the benefit here and now. Demonstrate how the system will make their daily work easier. They will then champion the change, becoming advocates for the new order.
- Middle management is the battleground. They need to be clearly categorized and dealt with accordingly:
- Negotiate firmly with the “politicians,” publicly fixing their areas of responsibility and deadlines.
- Isolate the “functionally powerless” from key project roles, transferring control to those capable of new ways of thinking.
In Lieu of a Conclusion
The hidden adversaries are not the developers or the consultants. They are the middle managers who either accept the new rules of the game and become agents of change, or they go underground, sabotaging the company’s future to preserve their comfortable past.
The ability to identify such an “adversary” in time and turn them from an enemy into an ally is the key skill for any team leading a project toward genuine, not just formal, success.
