Advisory & consulting
When should a business pause a digital programme?
Stopping work for a short review can be cheaper than carrying an obsolete plan to completion.
Published 25 September 2026
A business starts replacing its order system, then acquires another company with a different process and data model.
Freeze irreversible migration work, establish which operating model will prevail and then re-scope. Continuing simply to protect the original timetable may create a second replacement project.
Look for a broken premise
A programme deserves a pause when the business objective changes, the core data cannot be trusted, an essential decision-maker leaves or the expected benefit is no longer plausible. Ordinary delivery difficulties need management; a broken premise needs a fresh decision.
State what work can safely continue and what should stop. Preserve contracts, data and operational continuity while the decision is made.
Set a narrow review question and deadline
Ask what evidence would justify resuming, reducing or ending the programme. Examine a few representative workflows, the remaining cost and the consequences of each option. Do not turn a pause into an indefinite study.
Record the decision, its owner and the assumptions that now govern the work. A disciplined pause protects momentum by refusing to confuse activity with progress.