ERP implementations fail at a remarkable rate. Depending on which study you read, somewhere between 55% and 75% of large ERP programmes experience significant overruns, scope failures, or outright collapse. The reasons are well documented. The recovery paths are less so.
I've been brought into stalled ERP programmes at various stages of crisis. Some were recoverable with restructuring. A few needed to be stopped entirely and restarted on a different basis. What they all had in common was that the warning signs had been visible for months before anyone called for help.
A stalled ERP implementation is not a technology problem. It's a governance, accountability, and change management problem that happens to involve technology.
Why ERP Implementations Stall
The technical complexity of ERP is real, but it's rarely the primary cause of failure. The causes that actually derail implementations are almost always organisational.
Scope that was never properly defined. The implementation starts with a high-level brief and a vendor eager to begin. Detailed requirements emerge during build, contradicting earlier decisions. The programme expands, the timeline slips, and the budget follows.
Business ownership that was never established. IT owns the programme, business units are consulted occasionally, and nobody is accountable for whether the system actually gets used. Go-live happens. Adoption doesn't.
A vendor relationship with no accountability. The system integrator is paid by the day. Delays extend the engagement. There's no contractual mechanism to hold them to outcomes, only to activities.
Change management treated as a communications exercise. A few town halls, a training programme delivered in the final weeks, and a hope that people will adapt. They don't. Workarounds proliferate. The old system runs in parallel indefinitely.
Gartner's analysis of ERP failures consistently identifies organisational readiness and change management as the leading causes of implementation failure, not technology selection or vendor capability.
The ERP Recovery Playbook
Recovering a stalled ERP implementation requires a structured approach. The instinct is to push harder on the existing plan. That almost never works. Recovery requires stepping back, diagnosing honestly, and restructuring before re-accelerating.
Phase 1: Stop and Diagnose (Weeks 1–2)
Before any recovery action, you need an honest picture of where the programme actually is. Not the RAG status in the last steering pack. The reality.
This means interviewing key stakeholders without the programme team in the room, reviewing the contract and delivery schedule against actual progress, and assessing the vendor relationship with fresh eyes. The diagnostic should answer three questions: what is genuinely on track, what is recoverable, and what needs to be abandoned or redesigned?
Phase 2: Restructure the Foundations (Weeks 3–6)
Recovery almost always requires changes to governance, scope, or the vendor relationship. Sometimes all three.
Governance: Establish clear business ownership. The CIO cannot be the only executive accountable for an ERP implementation. Business unit leaders need skin in the game.
Scope: Cut what isn't essential for go-live. A smaller go-live that succeeds is worth infinitely more than a comprehensive go-live that fails.
Vendor: Renegotiate the engagement model if necessary. Move from time-and-materials to milestone-based payments where possible.
Phase 3: Re-baseline and Re-commit (Weeks 6–8)
Once the foundations are restructured, produce a revised plan that the programme team, the vendor, and the business can all commit to. This isn't the original plan with new dates. It's a genuinely revised plan built from the current reality.
The re-baseline should be presented to the steering committee with full transparency about what changed and why. Organisations that treat re-baselining as a failure tend to have programmes that never recover. Organisations that treat it as a necessary reset tend to deliver.
The question isn't whether your ERP implementation can be recovered. The question is whether you're willing to be honest about what it will take.
If your ERP programme is stalled or heading in the wrong direction, our team can conduct a rapid diagnostic and provide a clear recovery roadmap within two weeks. Book a 30-minute discovery call.