The Most Dangerous Transformation Status Is Green

A programme can be within tolerance today while its future delivery is becoming increasingly fragile. When that fragility sits behind a Green status, leadership may not intervene until the chance to influence the outcome has passed.

Leaders naturally focus on programmes reporting Red or Amber. Green ones get less scrutiny, on the assumption that Green means there is strong evidence the outcome will be delivered. Often it means something weaker: no milestone has been missed yet, spend is within budget, or the team still believes it can recover emerging delays. The reporting may be accurate while the confidence it creates is misplaced.

Green is often a statement about the present, not the future

Most programme reporting describes what has already happened. It records milestones completed, expenditure incurred, risks logged and issues raised during the reporting period.

These are necessary controls, but they don't necessarily tell leadership whether the programme is likely to achieve its intended outcome.

Consider a programme that has completed every milestone scheduled for the month. On that basis, a Green status may appear entirely justified. However, the same programme may also be carrying several unresolved conditions: a critical design decision waiting for executive approval for six weeks, specialist resources for the next phase not yet secured, a dependent technology programme that has moved its delivery date, user testing compressed to protect the go-live date, and a benefits case that assumes adoption levels for which no credible plan exists.

None of these conditions necessarily causes an immediate milestone failure. Collectively, however, they may make the future plan increasingly unrealistic.

This is the limitation of reporting delivery primarily against current tolerances. It can tell leadership whether the programme has failed yet, rather than whether failure is becoming more likely.

By the time the answer changes formally, the organisation may have significantly fewer options available.

Why programmes remain Green for too long

RAG status is rarely produced by a completely objective calculation. It combines evidence with judgement, and that judgement is often exercised by people who are personally accountable for delivering the programme.

Programme teams are usually close enough to the detail to understand where the difficulties sit. They may also genuinely believe those difficulties can be resolved. A delayed decision can be accelerated, a missed milestone can be recovered and additional resources can be found.

Individually, each assumption may be reasonable. The problem arises when the recovery assumptions accumulate without being reflected in the reported status.

A programme that is Green because it remains on plan is different from a programme that is Green because the team believes it can recover back to plan. Yet many dashboards present them in exactly the same way.

Culture makes this worse. Where a Red status is treated as an admission of failure, programme leaders have every reason to delay escalation. Sponsors may worry that changing status will undermine confidence, attract unwanted intervention or suggest that they aren't in control.

The reporting discussion then becomes a negotiation over colour rather than an assessment of delivery confidence.

Green is defended for as long as possible. Amber becomes a temporary position accompanied by a recovery plan. Red appears only when the failure is sufficiently visible that it can no longer be disputed.

Leadership sees a stable portfolio until several programmes appear to deteriorate suddenly. In reality, the deterioration was taking place over an extended period. The reporting system simply failed to represent it.

Separate today's performance from delivery confidence

The answer isn't to redesign the RAG definitions so that more programmes report Amber or Red. That changes the appearance of the portfolio without necessarily improving control.

Nor is the answer to introduce more detailed reporting. Transformation dashboards often contain substantial amounts of data already. The issue is whether that data helps leadership understand where outcomes are becoming less credible.

A more useful approach is to separate current performance from forward delivery confidence.

Current performance asks whether the programme is meeting its agreed milestones, budget and scope today. Delivery confidence asks whether there is sufficient evidence that the programme will continue to do so and ultimately achieve the intended outcome.

A programme may be Green against current performance while Amber against future confidence. That distinction gives leadership a much more useful signal than forcing both perspectives into a single colour.

It also changes the nature of the conversation. Instead of asking programme teams to defend their status, leadership can examine the assumptions that support it.

What must remain true for this programme to deliver successfully? Which of those conditions are becoming less certain? What evidence supports the current forecast? Where could executive intervention still improve the outcome?

Those questions are more valuable than debating whether a particular risk justifies moving from Green to Amber.

Six measures of delivery confidence

A credible view of delivery confidence requires forward-looking evidence. The exact measures will vary between programmes, but leadership should expect to understand several common areas.

Critical-path health should show whether the programme retains sufficient tolerance to absorb further disruption. A plan that is technically on schedule but has exhausted its contingency isn't in the same position as one with genuine flexibility.

Decision velocity should reveal whether material decisions are being made at the pace required by delivery. A programme can remain on plan for several weeks while the consequences of an unresolved decision accumulate downstream.

Resource readiness should examine whether the people and capabilities required for future phases are genuinely available, rather than simply named in a resource plan.

Dependency confidence should show whether other programmes, suppliers or business functions are likely to provide what the programme needs when it needs it.

Adoption readiness should test whether the organisation is prepared to use the new process, technology or operating model. A technically successful implementation with weak adoption remains a transformation failure.

Benefit confidence should assess whether the assumptions supporting the business case remain valid. Benefits shouldn't remain Green automatically simply because the delivery plan hasn't yet changed.

These measures don't remove the need for judgement. They provide a stronger evidence base on which that judgement can be exercised.

Early warning should be treated as evidence of control

Leadership teams often say that they want early escalation, but programme behaviour is shaped by what happens when concerns are raised.

If an early warning results in blame, unnecessary intervention or reputational damage for the programme sponsor, teams will naturally wait until the evidence is indisputable. By then, leadership may have lost the time it needed to act.

A controlled transformation should make it professionally safe to raise uncertainty while it can still be managed.

This doesn't mean tolerating vague concerns, habitual pessimism or weak delivery. Programme leaders should be expected to explain the evidence, the potential impact and the intervention required. They should also remain accountable for resolving the issue. The distinction is that early escalation is treated as responsible management rather than failure.

Transformation Management Offices have an important role here. Their job shouldn't be limited to consolidating the statuses submitted by individual programmes. They should independently challenge the evidence, identify patterns across the portfolio and expose where reported confidence is becoming inconsistent with delivery conditions.

A TMO that simply reproduces programme reporting can create a polished dashboard without improving executive control.

The executive questions behind a Green status

Leadership teams should be particularly curious about strategically important programmes that have remained Green for long periods despite visible complexity. Five questions can help test whether the status reflects evidence or optimism.

What evidence gives us confidence that the intended outcome will be achieved, rather than simply confirming that the programme is currently within tolerance?

Which assumptions must remain true for this programme to continue reporting Green?

What has become more difficult, uncertain or constrained since the previous reporting period?

Are any current milestones being protected by transferring risk into later phases of delivery?

If this programme were independently assured today, would the available evidence justify the same level of confidence?

The purpose of these questions isn't to catch programme teams out. It is to understand whether leadership's confidence is based on the underlying conditions required for success.

Green should be earned

A Green status should represent more than the absence of a recognised failure. It should indicate that the programme has a credible route to its outcome, supported by evidence across delivery, decisions, dependencies, adoption and value.

That is a higher standard than confirming that the programme remains within its current tolerances. It is also a more useful one.

Red programmes are visible. They receive attention, intervention and support. The organisation knows that something needs to change.

A fragile Green programme creates a different risk. It reassures leadership, avoids scrutiny and continues consuming time and investment while the opportunity to protect the outcome gradually reduces.

The safest programme is the one whose leadership understands its weak points and acts before they become failures.

Condor's perspective

At Condor, we believe transformation reporting should create foresight, not simply document performance after the event.

We work with leadership teams to establish evidence-based portfolio control, strengthen independent programme assurance and identify delivery deterioration early enough for executive intervention to make a difference. Past work includes £18m of in-year EBITDA impact for a UK telecoms client.

The real test of transformation control is how rarely leadership is surprised by what happens next.