When a programme is in trouble, the instinct is to act fast. Bring in more resource, push harder on the plan, escalate to the board. In my experience, that instinct makes things worse. Before you can fix a programme, you need to understand what's actually broken. That requires a diagnostic, done properly, before any recovery action begins.
A rapid programme diagnostic is a structured assessment of a programme's health, governance, delivery capability, and likelihood of success. It's not an audit. It's not a review meeting. It's a deliberate, time-boxed investigation designed to give decision-makers an honest picture of where a programme stands.
The diagnostic is the most valuable two weeks you can spend on a failing programme. Everything that comes after it is more effective because of it.
What a Rapid Diagnostic Is Trying to Answer
A good diagnostic doesn't try to answer everything. It focuses on the questions that matter most for recovery decisions.
1. What is the programme actually delivering? Not what the plan says. Not what the last steering pack reported. What is genuinely on track, what is at risk, and what has already failed silently?
2. Is the governance functioning? Are the right people making decisions? Are escalation paths clear and used? Is the steering committee making real decisions or performing governance?
3. Is the plan credible? Does the schedule reflect reality? Are dependencies properly mapped? Is the critical path understood by the people responsible for delivering it?
4. Is the team capable? Does the programme have the right skills in the right roles? Are there single points of failure? Is there over-reliance on specific individuals or vendors?
5. What does the stakeholder landscape look like? Who has lost confidence in the programme? Who is actively resistant? Who needs to be re-engaged before recovery can succeed?
The most revealing conversations in any diagnostic are with people two levels below the programme director. They know exactly what's broken. They've been trying to raise it for months.
How to Structure a Two-Week Diagnostic
| Days | Activity | Output |
|---|---|---|
| 1–2 | Document review: plan, risk register, steering packs, contracts | Initial hypothesis on key failure areas |
| 3–6 | Stakeholder interviews: sponsor, programme director, workstream leads, team members, vendors | Qualitative evidence on governance, capability, and confidence |
| 7–8 | Analysis and synthesis: cross-reference documents with interview findings | Validated picture of programme health |
| 9–10 | Report and recommendations: prioritised findings with clear recovery actions | Decision-ready output for the board or sponsor |
What the Output Should Look Like
The diagnostic report is not a list of everything that's wrong. A good diagnostic produces three things:
- A clear verdict on whether the programme is recoverable as currently structured, recoverable with restructuring, or should be stopped
- A prioritised list of the five to eight issues that most affect the programme's likelihood of success
- A recovery roadmap with specific actions, owners, and timelines
Anything longer than fifteen pages is too long. Decision-makers need clarity, not comprehensiveness.
Independence is non-negotiable. A diagnostic conducted by the programme team will find what the programme team is comfortable finding. According to the Association for Project Management, independent assurance reviews are significantly more likely to identify root causes of programme failure than internal reviews.
If you're not sure whether your programme needs a diagnostic, it probably does. The programmes that are genuinely healthy don't usually prompt the question. Our team conducts rapid programme diagnostics across the UK and GCC, with findings delivered within two weeks. Book a 30-minute discovery call.