Every experienced sponsor has lived this month. The programme that reported green for a year turns red in a single reporting cycle — and suddenly the recovery costs more than the programme.
The uncomfortable truth is that the programme did not fail in the month the report changed colour. It failed earlier, quietly, and the reporting system concealed it. The red report is not the failure; it is the confession.
How green conceals red
Across two decades of programme leadership and recovery, the same mechanisms appear each time, in some combination:
- The baseline stopped being real. Replanning absorbed the slippage; each new plan was achievable only if everything went perfectly from that day forward. Variance was reported against the newest fiction, not the original commitment.
- Reporting described activity, not position. “Workshops held, design progressing, engagement positive” — sentences that cannot be false and cannot be tested. Nobody asked the only questions that matter: variance against baseline, decision required, by when.
- Risks were recorded instead of managed. The register grew each month, immaculately formatted, while the actions column filled with “monitor”. A risk register that never changes a decision is a diary, not a control.
- Escalation carried a social cost. The first person to report amber honestly was asked to “get it back to green before it goes up”. So everyone waited for someone else to be first — until the programme ran out of months.
The discipline that prevents it
None of this is cured by better templates. It is cured by governance that makes honesty cheaper than optimism:
- One baseline, defended. Replanning is permitted; rebaselining is a governance event with a named approver and a recorded reason — never an administrative convenience.
- Reports that state position. Variance, decision required, date. If a report contains no number and no decision, it is not a report.
- Risk actions with owners and dates, reviewed for movement, not existence.
- Reward the first honest amber. The sponsor’s response to early warning determines every report that follows it. Thank the messenger publicly once, and the reporting system becomes truthful; punish them once, and it never is again.
How CS Corporation applies this
When we deploy into a programme, these disciplines are the first deliverable — instantiated inside the client’s own governance, not run alongside it. Where a sponsor suspects the reporting has drifted from reality, we begin with the Project Health Diagnostic: a fixed-scope, senior-led assessment of five controls — baseline integrity, risk management, dependency control, decision velocity and benefits tracking — producing a scored, evidenced position and a prioritised plan. It is designed to find the red before the report does.
If your programme has been green for a long time, that is either very good news or very old news. A diagnostic tells you which — while the difference is still affordable.