Advisory & consulting · JNAGA perspective
When should a business pause a digital programme?
Continuing a programme is a decision. It deserves as much scrutiny as starting one.
Published 25 September 2026
Imagine a system build is halfway through when a newly discovered handover means staff would still copy the same information twice after launch.
A short pause to test that handover may be less disruptive than delivering the planned screens and repairing the operating model later. Preserve completed work, record the choice and decide what evidence would justify resuming.
Watch for a change in the case for the work
A programme may be technically on schedule while its underlying assumption has weakened. The need may have changed, a dependency may be missing, or the team expected to adopt the change may have no capacity. These are not reasons to blame delivery; they are reasons to revisit the decision.
Distinguish ordinary learning from a fundamental change. New details are expected. A pause is warranted when continuing as planned would commit the business to a result that no longer addresses the original problem.
Make the pause deliberate
Name what will stop, what must continue safely and who can decide. Protect data, access and contractual obligations already in motion. Specify the question the pause must answer and a reasonable review point. An open-ended halt can be as costly as unexamined continuation.
Consider the options explicitly: revise the scope, test a smaller path, integrate with existing work or stop. Past effort matters for continuity, but it does not make the future commitment automatically worthwhile.
Resume with a changed plan
If the programme continues, update its outcome, responsibilities and next test. A pause has value when it changes the quality of the decision, not when it merely moves the same plan to a later date.