How to reset a stalled transformation

When a transformation grinds to a halt, it rarely fails for technical reasons. It is usually an alignment problem, and most stalls can be corrected if leaders act decisively.

Programme recovery is rarely about heroics. It is about identifying a handful of root issues, fixing them properly, and rebuilding momentum with clarity. My approach rests on four essentials.

1. A reality check against the business case

Test whether the benefits, costs and timelines still stack up. Benchmark against comparable programmes rather than internal opinion, and write down where things really stand: processes that do not fit the new system, data that is not flowing, integrations that were never scoped. This shows which assumptions broke.

2. Reset leadership alignment

Make sure the sponsor and executive team are united and visibly committed to the refreshed objectives. Misaligned executives almost guarantee failure, because competing priorities override programme decisions. If needed, have the steering committee publicly recommit.

3. Replan with discipline

Rebuild the plan from the point of failure. The existing budget is usually no longer valid. Re-baseline scope, budget and timeline around the highest-value outcomes, cut or defer low-value work, and tie every change to its business impact. A smaller, sharper plan with a credible return holds up better than a wishful one that still promises everything.

4. Rebuild ownership and engagement

Transformation cannot sit in a silo. Bring stakeholders and delivery teams back in with clear communication and accountability. Measure outcomes, not just activity: if you only track tasks on time and on budget, activity becomes the work.

Diagnose the few root problems, fix governance and funding, and communicate relentlessly. That is how most stalled programmes get moving again.

Scott Armstrong is a programme director who recovers and delivers ERP, finance, data and CRM transformation for large organisations. Talk to Scott about your programme.