Assurance & Reporting
The Most Dangerous Transformation Status Is Green
Red programmes get attention. Everyone knows they're in trouble, so they get the meetings, the money and the senior time.
Green programmes get left alone. That's fine if Green means the programme will deliver what it promised. Often it only means nothing has gone wrong yet.
A programme can hit every milestone this month and still be heading for trouble. If that risk sits behind a Green status, leaders tend to find out when it's too late to do much about it.
What we'll cover
Why a Green status looks backwards
Why programmes stay Green for too long
How to separate today's performance from delivery confidence
Six measures that show whether Green is earned
Five questions to ask about any Green programme
How to run a better status review
Why a Green status looks backwards
Most programme reports describe what has already happened: milestones completed, money spent, risks logged. That's useful. It doesn't tell you whether the programme will deliver.
Picture a programme that hit every milestone this month. Green looks fair. But it could also be carrying problems like these:
A key design decision has waited six weeks for sign-off
The specialists needed for the next phase haven't been secured
Another programme it depends on has moved its date
User testing has been squeezed to protect the go-live date
The business case assumes adoption that nobody has planned for
None of these breaks a milestone today. Together, they make the plan much harder to hit.
This is the limit of reporting against today's tolerances. It tells leadership whether the programme has failed yet. It says far less about whether failure is getting more likely. By the time the status formally changes, the organisation usually has fewer options left.
Why programmes stay Green for too long
RAG status is a judgement call, and it's usually made by the people running the programme. They know where the problems are and they believe they can fix them.
That belief is often reasonable. The trouble starts when recovery plans pile up and the status never changes. A programme that's on plan and a programme that hopes to get back on plan both show up as Green.
Culture makes this worse. Where Red is treated as failure, people delay raising it. The pattern usually looks like this:
Green is defended for as long as possible
Amber appears briefly, with a recovery plan attached
Red appears only when nobody can argue with it
From the top, the portfolio looks stable until several programmes seem to collapse at once. In reality they'd been sliding for months.
The reporting discussion becomes a negotiation over colour. Time goes on defending a status when it should go on understanding what's happening underneath it.
Separate today's performance from delivery confidence
Changing the RAG definitions won't fix this. Adding more reporting won't either. Most dashboards already have plenty of data.
A better approach is to report two things separately:
Current performance: is the programme meeting its milestones, budget and scope today?
Delivery confidence: is there evidence it will keep doing so and deliver the outcome?
A programme can be Green on the first and Amber on the second. That tells leaders far more than one colour. It also changes the conversation. Instead of asking teams to defend a colour, leaders can ask what has to stay true for the programme to succeed.
Six measures of delivery confidence
The exact measures vary by programme, but most should be able to show:
Critical path health: is there still room to absorb another delay?
Decision speed: are big decisions being made fast enough?
Resource readiness: are the people for the next phase actually available?
Dependencies: will other teams, suppliers and programmes deliver on time?
Adoption readiness: is the business ready to use what's being built?
Benefit confidence: does the business case still hold?
None of this removes judgement. It gives judgement better evidence to work with.
A plan that's on schedule but has used all its contingency is in a weaker position than one with room to spare. A programme can stay on plan for weeks while an unresolved decision quietly piles up problems further down the line. These measures make that visible before it shows up in the milestones.
Make early warnings safe
Leaders say they want problems raised early. Then someone raises one and gets blamed. People learn fast.
Raising a risk early should count as good management. That still means bringing evidence, the likely impact and a clear ask. It doesn't mean tolerating vague worry.
A Transformation Management Office (TMO) has a big part to play here. Its job is to test the evidence behind each status and spot patterns across the portfolio. A TMO that only collects and reformats programme updates adds polish without adding control. We go into this in more detail in Your Transformation Dashboard Is Probably Lying to You.
Five questions to ask about any Green programme
What evidence says we'll achieve the outcome, beyond being within tolerance today?
What has to stay true for this programme to stay Green?
What has got harder or less certain since the last report?
Are we hitting today's milestones by pushing risk into later phases?
If someone independent reviewed this today, would they agree with Green?
The point is to check that leadership's confidence rests on something real.
How to run a better status review
Most status reviews walk through each programme's colour in turn. A better review starts with the evidence:
Start with the programmes where confidence has dropped, whatever their colour
Ask what has changed since the last review
Look at open decisions and who owns them
Check dependencies across the portfolio, beyond each programme on its own
Agree specific actions, owners and dates before the meeting ends
Spend the time on the handful of programmes where leadership can still change the outcome. The rest can be handled by exception.
Green should be earned
A Green status should mean the programme has a credible route to its outcome, backed by evidence. That's a higher bar than "nothing has failed yet".
Red programmes get help. A fragile Green programme gets left alone while time and money run out. The real test of transformation control is how rarely leadership is surprised by what happens next.
Frequently asked questions
What does a Green RAG status mean?
In most organisations, Green means a programme is within its agreed tolerances for time, cost and scope. It describes current performance. It doesn't always tell you whether the programme will deliver its intended outcome.
Why do programmes go from Green to Red so quickly?
Usually they don't. The weaknesses build up over months: delayed decisions, stretched resources, squeezed testing. The status only changes when the problem can no longer be argued with.
What is delivery confidence?
Delivery confidence is a forward-looking view of whether a programme will achieve its outcome. It's based on evidence such as critical path health, decision speed, resources, dependencies, adoption and benefits.
Who should challenge a programme's RAG status?
A Transformation Management Office (TMO) or an independent assurance team. They're close enough to understand the programme and far enough away to test the evidence objectively.
How Condor helps
We help leadership teams set up evidence-based portfolio reporting, run independent programme assurance and spot trouble early enough to act on it. Past work includes £18m of in-year EBITDA impact for a UK telecoms client.
If your dashboard is all Green and you still feel uneasy, we should probably talk. Get in touch
When Execution Matters, We Deliver.
