The status is green, but teams disagree: can management trust the programme report?

A colour is the end of compression, not the beginning of truth

Programme status has to compress complexity. That is its purpose. Compression becomes dangerous when the colour is treated as a fact while business, technology, vendors and operations use different foundations. Green may simultaneously mean milestones formally achieved, spend within tolerance, critical risks not yet escalated, or a date still possible under additional assumptions. Those claims are not equivalent.

Leadership should therefore follow neither the loudest pessimist nor the official colour by reflex. It should test how the assertion was produced. The UK's Infrastructure and Projects Authority requires major programme data to be current, accurate, complete and consistent. The principle travels well: status should rest on a traceable information chain.

Four tests for a defensible status

The first test is definition. Which criteria produce green, amber or red? Are time, cost, scope, value, risk, business readiness and technical quality assessed separately or blended into one colour? Were tolerances agreed in advance? Without definitions, colours cannot be compared across periods or workstreams.

The second test is data lineage. Which source systems, decisions, tests and owners support the assertion? Are manual judgements labelled? Can the forum trace an important dashboard value back to the evidence that produced it? The more heavily status is aggregated, the more important that traceability becomes.

The third test is dependency. A workstream may be green and still fail because of an external decision, migration, architecture component or scarce operational resource. Overall status must expose the relationships whose failure materially changes the outcome or date. A list of isolated workstreams is insufficient.

The fourth test is contrary evidence. Which facts would disprove the current assessment? Are there competing signals in defects, throughput, unresolved decisions, vendor forecasts, control testing or workforce capacity? Defensible reporting searches for disconfirming evidence instead of treating it as a communication problem.

Why teams disagree

Disagreement can come from different objects of measurement. Technology may measure system function, the business process capability, finance the remaining economic case, and the vendor contractual deliverables. Each can be correct within its own frame. Management must relate those frames to the same decision.

Incentives can also amplify disagreement. A team may want to avoid escalation, a supplier to reach the next milestone, or a sponsor to protect a communicated date. That is not an accusation. It is a reason to separate claims from interests and to test evidence independently where a wrong decision would have material consequences.

Reporting may also lag reality. Monthly figures reflect choices and problems that arose weeks earlier. Leading indicators such as unresolved dependencies, repeated retesting, falling throughput or deferred design decisions can already shape the next period while the current colour remains unchanged.

From status report to Decision Memorandum

An executive forum does not need more detail; it needs better compression. A Decision Memorandum should identify the decision, show the few claims supporting it, distinguish evidence from gaps, represent contrary positions fairly, and state the consequences of Continue, Reset and Stop. Conditions, owners and decision dates make the recommendation testable.

If a green status survives that examination, it becomes more credible. If it does not, the answer is not automatically red or Stop. The appropriate response may be a bounded evidence sprint, conditional continuation or a reset of specific prerequisites. Independent review is not intended to manufacture a more dramatic colour. Its purpose is to structure uncertainty so that management can make a decision it can defend.

Questions for the next steering committee

Before the meeting, the sponsor should request three things: the definition behind the colour, the two strongest items of supporting evidence, and the two strongest items of contrary evidence. Every critical dependency should also have a decision date and an accountable owner. This short discipline exposes contradictions earlier without turning reporting into a data graveyard.

The forum should also define what new evidence would change the status. If green survives almost any development, the colour is not describing a controllable reality. A status model is useful when it responds to new facts, marks uncertainty clearly and directs leadership attention to the points where action can still change the outcome.