ERP Implementation Rescue
An ERP implementation that has stopped moving is one of the most expensive problems an organisation can carry. The licences are already bought. The integrator is still invoicing. The business has already absorbed months of disruption. And the go live date has moved so many times that nobody in the building believes the next one either.
Elisabeth Butler is an interim IT programme director who steps into ERP programmes that have gone wrong and gets them delivered. The work is independent by design: no allegiance to the system integrator, no internal politics to protect, and no reason to give the board anything other than an accurate picture.
ERP Rescue Services
ERP rescue is not a review that produces a report and leaves. It is hands on programme leadership through the recovery itself. The engagement covers four things.
- Independent diagnosis: A rapid assessment of governance, vendor performance, scope control, data readiness, testing status, financial position and adoption risk. Typically two to three weeks, ending in a clear statement of what went wrong and what can be salvaged.
- Governance restructure: Putting decision making authority, change control and reporting back in place so the programme stops drifting and the board regains visibility.
- Vendor control: Separating contractual dispute from delivery, holding the integrator to measurable commitments, and rebuilding a working relationship where that is possible.
- Delivery to go live: Owning the recovery plan through to a system that is live, adopted and handed over to a stable internal team.
Signs Your ERP Implementation Needs Rescuing
Programmes rarely fail suddenly. They deteriorate through a recognisable pattern, and the earlier the intervention, the more of the investment can be protected.
- The go live date has slipped more than once and the new date carries no more confidence than the last.
- Status reporting has turned green while the people doing the work privately describe the programme as red.
- The relationship with the implementation partner has become contractual and defensive rather than collaborative.
- Costs have moved materially beyond forecast and nobody can explain precisely where the money has gone.
- Data migration keeps being deferred to a later phase because the underlying data quality problem has not been faced.
- Scope keeps expanding through informal agreement rather than controlled change.
- Key internal people have started to disengage, and some have already left.
Why ERP Implementations Fail
In the great majority of cases the software is not the problem. ERP failures are governance and change failures that show up as technical symptoms.
Scope is agreed loosely at the start and then expands without anyone owning the cumulative effect on cost and timeline. Decisions that need a senior owner sit unmade for weeks in steering meetings. The system integrator is left to assess its own progress, so problems surface late. Data migration is treated as a technical task at the end rather than a business cleansing exercise from the beginning. And business process change and user adoption are underfunded relative to the configuration work, so a technically working system lands in an organisation that will not use it properly.
Recovery works because these are addressable problems. What they need is someone with the authority to name them accurately and the experience to fix them in the right order.
ERP and CRM Rescue and Recovery
The same discipline applies to CRM programmes and to combined ERP and CRM transformations. Both are large business change programmes carrying substantial process, data and adoption risk, and both tend to fail for the same governance reasons rather than for purely technical ones. Where an organisation is running both in parallel, the interdependencies between them are frequently where the recovery has to start.
Why Independent Recovery Works
Internal programme managers are often unable to lead a recovery, however capable they are. They are too close to the existing dynamics, the vendor already regards them as part of the dispute, and stakeholders have usually stopped trusting their reporting. Asking the same team to diagnose its own programme rarely produces the honest assessment that recovery depends on.
An independent interim director arrives without that history. Elisabeth has recovered programmes across enterprise technology, retail, financial services, heritage and the public sector, and has no commercial interest in any particular outcome other than delivery.
Common Questions
Can a failing ERP implementation be recovered, or should we start again?
Most can be recovered. Starting again is rarely the cheapest route, because the investment already made in configuration, data and process design usually retains real value. The honest assessment of what is salvageable should come before any decision, and it needs to be independent of both the internal team and the implementation partner.
How long does an ERP rescue take?
The diagnostic phase is typically two to three weeks and produces a costed recovery plan. The recovery itself depends on programme size and how far it has drifted, though stabilising governance and vendor performance usually shows measurable improvement within the first two months.
When is the right time to bring in outside help?
The usual trigger points are a second slipped go live date, a vendor relationship that has turned adversarial, costs materially above forecast without clear explanation, or a board that no longer trusts the reporting. If the same issues recur in consecutive steering meetings without resolution, the programme is unlikely to correct itself.
Related reading:
Related case studies:
Related services:
Is your ERP implementation in trouble?
An initial conversation costs nothing and will tell you whether the programme is recoverable.
Get in touch