Insights

Recovering a critical programme

Programme recovery works when facts are separated from narrative, the critical path and dependencies are visible, and every decision has an owner and deadline.

A direct, confidential first conversation. No presentation required.

Programme recovery works when facts are separated from narrative, the critical path and dependencies are visible, and every decision has an owner and deadline.

1. Establish a credible baseline

Use accepted deliverables, verifiable progress, contractual commitments, actual capacity and constraints. Aggregate completion percentages are not enough if they do not show what is genuinely usable.

2. Rebuild the critical path

Map technical, decision, vendor, environment, data and change dependencies. Give each dependency an owner, required date, risk signal and viable fallback.

3. Govern decisions and recovery

Open a decision log with options, recommendation, delay impact, decision maker and date. Choose Scrum, predictive or hybrid delivery according to uncertainty and constraints, then agree scenarios, trade-offs, quality gates and exit criteria.

Signal Intervention
Unverifiable status Baseline on accepted deliverables
Dependencies without owners Map and named accountability
Decisions stalled Decision log with deadlines

FAQ

Direct answers

Will Agile rescue a late programme?

Not by itself. A new label does not remove dependencies, open decisions or insufficient capacity.

Must the PMO be replaced?

Not necessarily. Its mandate, information and decision cadence often need to change.

What is the first deliverable?

A shared view of current reality, urgent decisions and recovery options with explicit impact.

← Insights

Facing a complex decision or a programme that must change pace?

Let us frame the context, what is at stake and the next useful decision.

Request a confidential conversation ↗