Programme recovery is the structured intervention applied to a technology implementation programme that has entered distress — typically characterised by significant schedule slippage, budget overrun, quality deficiencies, or a combination of all three, to the point where the programme cannot self-correct without a structured reset. A programme in distress does not recover by working harder or extending the timeline; it requires a diagnostic that identifies the root causes of the distress, a reset that establishes a realistic new baseline, and governance changes that prevent the conditions that caused the distress from recurring. Programme recovery is not programme acceleration; it is programme stabilisation followed by a controlled return to delivery.
Why This Matters in GCC and Egyptian Enterprise Programmes
Programme recovery in GCC enterprise contexts frequently involves the additional complexity of managing the recovery alongside an active regulatory deadline. A Saudi enterprise with an Oracle EPM implementation that is twelve months behind schedule and has a ZATCA reporting compliance deadline in three months cannot recover at the programme’s natural pace; the recovery must be triaged against the compliance requirement. Recovery planning in this context requires an explicit decision: which programme outputs are needed for regulatory compliance, what is the minimum viable delivery that satisfies the compliance deadline, and what is the recovery plan for the remaining scope after the compliance milestone is met. This triage decision is a steering committee decision, not a programme team decision.
What Good Looks Like
An effective programme recovery begins with an independent diagnostic — a structured assessment by a party that was not involved in the programme’s delivery, that identifies the root causes of the distress without the bias of the people whose decisions contributed to it. The diagnostic produces a recovery report with three outputs: a current state assessment (what is the actual programme status, stripped of optimistic reporting), a root cause analysis (what decisions and conditions produced the distress), and a recovery plan (what changes are required — to scope, team, governance, and commercial arrangements — to return the programme to a viable path). The recovery plan is reviewed by the steering committee and approved before the recovery programme begins; a programme that enters recovery without a steering committee-approved plan is not recovering — it is continuing with additional urgency.
What Organisations Get Wrong
The failure that most consistently delays the start of an effective recovery is the programme sponsor’s reluctance to acknowledge programme distress officially — because doing so involves acknowledging that decisions they made (the SI selection, the scope commitment, the timeline) contributed to the failure. In GCC enterprise contexts, where the programme sponsor may be reporting to a family owner or a board that approved the investment, acknowledging a programme in distress has personal consequences that create a strong incentive to delay the acknowledgment. The delay compounds the distress: issues that could be resolved with a four-week recovery programme require a six-month recovery programme twelve weeks later. The cost of the recovery — in time, money, and organisational credibility — is directly proportional to how long the distress is managed informally before it is formally acknowledged.
How Loop Wise Solutions Approaches This
Loop Wise Solutions provides programme recovery advisory as an independent engagement — typically engaged directly by the programme sponsor or board, not through the incumbent SI. We conduct the diagnostic independently, present the findings to the steering committee without softening for comfort, and design the recovery plan around what is achievable rather than what is desirable. Our involvement in recovery engagements frequently includes renegotiating the commercial arrangement with the incumbent SI — where the distress has a contractual dimension — as well as the governance and delivery changes required for the recovery.
