DECISION GUIDE
A stalled implementation needs evidence before it needs more activity.
Recognise when scope, data, design, testing, ownership or confidence require a controlled recovery assessment.
Read the practical answerTHE SHORT ANSWER
More delivery effort will not solve an unresolved programme decision.
Recovery starts by protecting the operation, establishing what is actually complete and trusted, and deciding whether to recover, replan or stop parts of the work.
WHAT TO EXAMINE
Signs the programme needs intervention.
Status cannot be proven
Progress is reported through activity rather than accepted scenarios.
Scope keeps moving
Important requirements and boundaries remain implicit.
Data is late
Migration, reconciliation and ownership are not evidenced.
Users lack confidence
Testing and training do not reflect real work.
WHY THE DECISION MATTERS
Continuing without a reliable baseline deepens sunk cost and disruption.
Teams can spend more while defects, data, customisation and missing decisions make a safe go-live less likely.
A practical route forward.
- Stabilise immediate business and data risks.
- Review scope, configuration, defects, data and tests.
- Reset decision ownership and acceptance criteria.
- Choose a sequenced recovery, replan or stop route.
Replace reassurance with a fact-based recovery decision.
Bring the current plan, systems and unanswered questions. We will help test the decision.