Clyr Consulting

When a programme
needs a recovery review.

A missed milestone is a signal to investigate. The pattern behind it matters more than the colour on a status report.

1. The dates change, but the assumptions do not

Moving a milestone does not resolve the constraint that caused the delay. Ask what has changed in scope, capacity, dependencies or approach to make the revised date credible.

2. Progress is difficult to demonstrate

Activity is easy to report. Accepted outputs are more useful. Ask which deliverables have met their acceptance criteria and what evidence supports the reported position.

3. Decisions stay open

An unresolved decision can quietly hold up several teams. Identify the decision owner, the options, the information needed and the date by which a choice must be made.

4. Dependencies appear late

If teams repeatedly discover they are waiting on one another, review the integrated plan. A list of individual workstreams is not enough when delivery depends on hand-offs between them.

5. Success means different things to different people

The sponsor may be expecting a business outcome while the team is delivering a technical milestone. Reconfirm the intended outcome and how the organisation will recognise and own it.

What a recovery review should produce

A useful review produces a shared view of the position, credible options and specific actions with owners. It should make the trade-offs visible, including any change to cost, scope, time or expected benefit.

Start by asking for delivery evidence, the current decision log, key dependencies and the business case. Use those inputs to decide whether the programme needs a targeted intervention or a broader reset.

Explore Clyr’s programme recovery support.

Start with the challenge.

Let’s discuss the support your organisation needs.

Talk to Kieron ↗