Restarting a transformation that has lost momentum

Updated 17 October 2026

A programme that has lost momentum does not necessarily need a relaunch. It may need a decision that leadership has been postponing.

The difficult question is whether the organisation should still pursue the original investment case. Since approval, costs may have changed, a dependency may have failed or the business may have moved on. Asking the team to work harder cannot repair an assumption that no longer holds.

Before announcing a recovery plan, establish what is still worth delivering and what has made delivery difficult.

Reopen the investment case

Compare the original expected benefits with the latest evidence. Check the cost to complete, including the operational disruption of implementing the remaining work. Separate past spending from future commitments. Money already spent explains the history; the next decision concerns what further spending is justified.

Some benefits may still be achievable with a narrower scope. Others may depend on work that is no longer funded. Make those connections visible before retaining the original targets.

Give leadership genuine options. Continuing unchanged, reducing scope, pausing and stopping should each have a clear consequence. An assessment that recommends continuation regardless of what it finds is unlikely to restore confidence.

Trace the work to the unresolved decision

Take one delayed outcome and follow the work backwards. Which team is waiting? What do they need? Who has authority to resolve it? How long has the issue been open?

Consider an illustrative finance transformation. A shared reporting platform is ready for testing, but subsidiaries use different account definitions. Technology staff keep revising the configuration while finance leaders have yet to agree the common definitions and permitted exceptions. Calling this a technical delay obscures the decision required.

In that situation, another status meeting adds little. The recovery action is to bring the responsible finance executives together with a clear proposal and an agreed route for resolving exceptions.

Match the restart to actual capacity

A credible recovery plan has to fit the people available. Name the operational staff needed for testing, training and implementation, then confirm what other work will move to release their time.

Where capacity is insufficient, reduce scope or change the sequence. Keeping every initiative while compressing every deadline simply transfers the problem back to the team.

Select a small number of outcomes that can be completed and checked. Give each a responsible executive, the dependencies it needs and a date for the next decision. Avoid promising a rapid recovery before those commitments have been agreed.

Rebuild trust through reporting

People who have heard several relaunches will judge the next one by what leadership does. Explain what has changed in the plan, what has been stopped and which difficult choices have finally been made.

Report against the revised commitments. Keep the original baseline visible so that a new schedule does not quietly erase the history. Raise new problems early, with the consequence of waiting and the decision needed.

A restart is credible when the revised commitments can be checked. Keep the next review focused on delivery against those commitments and on any choices the team still lacks the authority to make.