A programme can be reported as stable while the underlying delivery system is deteriorating. This anonymised scenario-based case study combines recurring delivery conditions observed by Enigma’s senior practitioners across public and private-sector programmes. It does not describe or identify a single client engagement.
The situation
A supplier-led technology programme had entered a prolonged recovery cycle. Milestones had moved more than once, action plans were growing, dependencies were increasingly compressed and senior stakeholders were receiving broadly reassuring status reports. The supplier had a recovery plan, but the client lacked an independent basis for judging whether that plan was credible.
The assurance problem
Recovery plans often confuse more management activity with restored deliverability. Additional meetings, workstreams, actions and revised dates can create the appearance of control without changing the underlying constraints. The client therefore needed to know whether the programme was genuinely recovering or merely producing a new narrative around the same risks.
The independent assurance approach
Enigma established an evidence baseline across schedule logic, critical dependencies, testing, defects, data, architecture, supplier commitments, resource assumptions, decision latency and governance. The supplier’s recovery claims were then tested against that baseline. The focus was not whether actions existed, but whether each action changed an evidenced constraint and whether the revised plan remained internally coherent.
The review aligned to Enigma’s Programme Health Checks and Recovery service and Supplier Delivery Assurance approach.
What the evidence showed
The key weaknesses were found at the interfaces between workstreams. Individual teams could report progress while the programme-level critical path remained exposed. Dependencies had been accepted without clear evidence of completion. Some recovery dates relied on optimistic assumptions about defect closure, business availability or supplier throughput. Status reporting described intention more confidently than evidence justified.
The governance intervention
Recovery governance was reframed around a small number of explicit conditions: what had to become true, how it would be evidenced, who owned the evidence and by when. Supplier statements were treated as inputs, not assurance conclusions. Programme status was linked to demonstrated closure of the constraints that had caused the recovery problem in the first place.
Those controls reflect Enigma’s Decision Condition Framework and Closure Verification Standard.
Why this mattered
A credible recovery plan must change the probability of successful delivery. If it merely changes dates and actions, it is not a recovery plan. Independent challenge gives the client a defensible basis for distinguishing genuine recovery from schedule re-baselining.
The lesson
The most dangerous point in a troubled programme is often after a recovery plan has been agreed, because governance pressure reduces while the evidence may still be weak. Recovery should be judged by risk reduction and restored delivery capability, not by the existence of a plan.