Protect the remaining investment by determining whether recovery is still viable before committing further capital, time, and executive credibility to a failing path.
Replace fatigue, optimism, and institutional momentum with a clear recovery position that leadership can explain and defend under scrutiny.
Define the most defensible next move — whether that means stabilizing, restructuring, resetting, or exiting — before further losses compound.
When the delivery narrative and status reports are no longer enough.
Provide an external assessment of whether the current recovery position still holds up under evidence, separate from the existing narrative or reporting cycle.
Help leadership determine whether the initiative should continue under recovery, be re-scoped, reset, or stopped before further loss compounds.
Produce a concise, board-ready recovery position that can be explained and defended under sponsor, investment, or oversight scrutiny.
Use this review when delivery, Program and or Project, remains active, but confidence in control, alignment, or recoverability has significantly weakened.
We assess whether the initiative still has a realistic path back to control — not as a plan, but as an executable outcome.
We identify where reported confidence, governance narratives, or recovery claims no longer align with the actual delivery condition.
We surface the points where dependencies, interfaces, authority, coordination, or commercial conditions have become barriers to meaningful recovery.
We determine whether the organization still has enough control, optionality, and salvageable value to justify continued recovery effort.
| Document Type | Description & Evidence Provided |
|---|---|
| Recovery plans and baselines | Recovery plans, revised delivery baselines, and milestone changes that show how the initiative is expected to regain control. |
| RAID and unresolved issue patterns | Recorded risks, assumptions, issues, and dependencies — including whether critical issues are being resolved, recycled, or merely carried forward. |
| Action and escalation trails | Evidence of how recovery concerns are being raised, owned, escalated, and acted on across delivery and governance layers. |
| Governance packs | Steering committee, PMO, sponsor, and oversight materials that show how recovery is being governed and how confidence is being reported. |
| Milestone movement | Shifts in key dates, recovery checkpoints, and critical path events across recent reporting cycles. |
| Reporting deltas | Differences between successive reports, dashboards, or governance packs that indicate where the narrative is changing faster than the delivery condition. |
| Delivery flow and work-in-progress evidence | Evidence showing whether recovery activity is translating into meaningful movement, or simply creating visible effort without material stabilization. |
| Dependency chains and interface breakdowns | Cross-team, vendor, infrastructure, commercial, or regulatory dependencies that may now be preventing meaningful recovery. |
| Commercial and commitment evidence | Evidence of how contractual constraints, partner behaviors, delivery commitments, and sequencing choices are shaping the recovery path. |
| Contract Integrity and Variation Records | Master contracts, statements of work, amendments, and change instruments showing how commercial terms and obligations have evolved during recovery. |
| Structural testimony and narrative alignment | Targeted stakeholder evidence used to identify contradictions, alignment gaps, or structural barriers that are not visible in formal reporting. |
| Dimension | Focused | Integrated | Strategic |
|---|---|---|---|
| Primary Use | Used when recovery concern is concentrated in one project, release, or contained failure point | Used when recovery issues are spreading across delivery streams, dependencies, or stakeholder groups | Used when the initiative is high-consequence and leadership needs an executive-grade recovery position |
| Typical Scope | Single initiative, release path, or contained recovery scenario | Cross-functional project or programme environment with shared recovery pressure | Enterprise-critical programme or transformation initiative in active distress |
| Decision Supported | Recover, intervene, or contain | Re-scope, re-baseline, stabilize, or recover | Reset, protect, exit, or stop |
| Confidence Delivered | Directional | High confidence | Board-level confidence |
| Value at Stake | Prevent near-term continuation error and avoid wasted effort on a failing path | Restore control across a fragmented recovery environment | Protect major investment, sponsor credibility, and residual value |
| Internal Effort | Minimal | Low–Moderate | Moderate |
| Time to Insight | 5–7 days | 7–10 days | 10–14 days |
A clear, evidence-based decision indicator showing whether the initiative should Recover, Recover with Conditions, Re-scope, Reset, or Exit.
A focused assessment of where recovery remains possible, where it is structurally weak, and where it has already broken.
A prioritized set of actions, ownership shifts, and decision thresholds required to restore control or execute a defensible pivot.
When a major technology initiative is deteriorating and the organization needs an independent view of whether it can still be recovered.
When personal or executive accountability is tied to an initiative whose delivery story no longer feels credible.
When recovery has become active, but no longer appears to be restoring control.
When continued investment requires a defensible basis and the organization must determine whether further capital should still be committed.
When vendor conditions, commercial leverage, or contractual realities may now determine whether meaningful recovery is still possible.
When delivery instability or deteriorating governance is creating material risk exposure that requires an independent assessment before escalation or disclosure.
