How to Recover a Stalled IT Programme

I have been brought into more stalled programmes than I can count. The symptoms are always the same: missed deadlines, budget overruns, demoralised teams, frustrated stakeholders, and a general sense that nothing is moving. The instinct is to add more people, extend the timeline, or bring in a new vendor. None of these address the actual problem.

Stalled programmes are almost always stalled because of governance and leadership failures, not resource shortages. The first thing I do when I arrive is assess the governance. Who is making decisions? How are risks being managed? Is there a single point of accountability? In most cases, the answer to that last question is no, and that is the root cause. The pattern is remarkably consistent, as I explain in why organisations fail at IT programme delivery.

The second thing I do is reset expectations. I have honest conversations with every key stakeholder about where the programme actually is, not where the last status report said it was. This is uncomfortable but essential. You cannot recover a programme if everyone is working from fiction.

The third thing is to create a recovery plan that focuses on quick wins. Not a grand redesign of the entire programme. Small, visible deliverables that demonstrate momentum and rebuild confidence. Once the team sees that progress is possible, energy and morale return surprisingly quickly.

Programme recovery is not about working harder. It is about working differently. Better governance, clearer accountability, and honest communication will unlock more progress than any amount of additional resource. Elisabeth's programme recovery service is built around exactly this approach. She used it to bring an enterprise ERP programme back from the brink after months of stalled delivery. Getting governance right was the essential first step.

If your programme has stalled, talk to Elisabeth about getting it moving again.