Almost no failed implementation was “unlucky”. Even if the success record is dismal: Between 55% and 75% of implementations miss their expected ROI, nearly one in five (!) get abandoned outright; and, even worse, one in six threaten the financial stability of the organization undertaking them. These numbers are treated as proof that large projects are inherently risky, much like weather. They are not. A project does not collapse the way a storm arrives. It collapses because specific, knowable things were done wrong, were left undone, or treated as not important.
Alexios E. Kotsilinis, founder of adaptiveX Consulting, has built his reputation rescuing exactly these implementations. “Completing a project successfully is not rocket science,” he states. “Implementations are governed almost entirely by the simple law of cause and effect.” Projects fail not because the law is unknown, but because leaders under pressure stop respecting it.
You Cannot Fix What You Cannot See
The first failure in a troubled project is a failure of visibility. Leaders react to whatever is loudest – not to whatever affects the project most – mainly because they don’t have full visibility of how the project is going. Real visibility must cover four areas: the solution, the implementation process, the data put into the solution, and the team operating it. And none of it is possible without clear success criteria: What are the business objectives? What is the organization willing to spend? When does the system need to be live? Who from the business is designing the future processes, because the people defining how the company will operate after go-live should be its best, not whoever is available.
Alexios offers a warning to anyone inheriting a rescue: “Do not assume this clarity exists. A startling number of projects launch without it, and even where it once existed, conditions have shifted since. Re-examine all of it, establishing and then build the ability to measure against it.
When you do, the red flags will become very visible, and it is rarely one thing. A project in distress is usually losing in several places at once, which is exactly why visibility matters more than instinct.
Stabilize Before You Accelerate
The instinct when a project is behind is to push harder and catch up to the original plan. This is the most reliable way to make a struggling project worse. The first objective of a rescue is not to catch up. It is to stop the bleeding, which means narrowing focus to the areas doing the most damage and correcting them before attempting to recover lost ground.
Further, there is a human ceiling here that leaders ignore at their cost. People have a limited capacity for change, and a rescue that tries to fix everything at once spends that capacity recklessly, producing burnout and a deeper chaos than the one it set out to solve.
Rebuild Trust
Stabilization also sets up the part of a rescue unrelated to the process. When a project fails, morale breaks down in a specific direction, and trust goes along with it. Trust to project itself, the team, to the process, to the company. At that point, project sponsors should reestablish why we’re doing this. Why is this so important? What are the benefits for the company, but also, what are the benefits for the team. Personal benefits. Because burned-out people become less motivated by what is good for the company and more and more motivated by what is good for them – not out of malice but out of instinct.
The Bravest Decision Is Sometimes to Stop
The most important judgment in any rescue is the one most leaders avoid, because it questions the premise of the rescue itself. Not every project should continue in its original form, and in Alexios’ experience, most should not. If the project can still deliver its intended value, as it was originally planned, rescue it with a clear recovery plan. If the original plan no longer fits current conditions, which is true in the vast majority of cases, reset it. And if the project no longer supports the business at all, stopping it is the responsible decision.
This is where courage becomes a technical requirement rather than a virtue. Making that call well depends on predicting where the project will land at its conclusion and surfacing that prediction months in advance, while the organization still has room to act. That demands giving executives hard, honest, and unvarnished data, even when it is not what they want to hear.
Rescuing a failing project comes down to four disciplines and one quality. Visibility & measurement, structure, executive sponsorship, and courage to tell the truth about project status and projected outcome. The leaders who master that build organizations where failure gets caught early, named plainly, and corrected before it costs budget, trust, and momentum. All of which are far harder to rebuild than they ever were to protect.
Follow Alexios E. Kotsilinis on LinkedIn or visit adaptiveX Consulting for more insights on project rescue, implementation strategy, and the disciplines that turn failing initiatives into recoverable ones.
