When the Report Is Green and the Programme Is Failing
By the time the report finally turns amber, the amber is not an early warning — it is a confession that could no longer be delayed.
Executive Summary
Every programme of any scale produces reports, and yet those who commission the reports are often the last to learn that a programme is in trouble. The distance between the volume of reporting a programme generates and the quantity of genuine understanding it yields is among the most durable features of large-scale change. It is the subject of this essay.
The central argument is that reporting and insight are not two points on a single scale, where enough of the first eventually turns into the second. They are different activities that have been permitted to share a name. Reporting is the production of reassurance, on a fixed cadence, in a fixed format, for an audience that has little time. Insight is the production of understanding, which keeps no schedule and fits no template. Because the status report is the instrument to hand, and because it is comfortable, we have quietly agreed to treat the two as equivalent. They are not, and the gap between them is precisely where programmes fail slowly and in plain sight of their own governance.
What follows examines why that gap opens, why it survives among capable and well-intentioned people, and what a practitioner can do to narrow it. The short version is that the gap is structural rather than personal. It is sustained by the cadence of reporting, by the format of the report, by the incentives acting on the people who compile it, and above all by the information asymmetry between those who do the work and those who oversee it. None of these forces is a failing of character; each is a feature of how programmes are organised. That is why exhortations to report more honestly achieve so little, and why the reform has to be structural too.
The status report is not a window onto the programme. It is an artefact the programme produces about itself — and like every such artefact, it is shaped as much by who will read it as by what is true.
The Comfortable Fiction of the Status Report
Consider what a status report is actually for. In principle it exists to inform a decision: to tell a sponsor or a programme board what is happening so that they can act. In practice, by the time most reports reach the board, the questions they might have informed have already been settled. The report does not drive the decision; it ratifies a position already held. It becomes a ritual of reassurance, and everyone in the room understands the ritual even if no one names it.
The fiction is comfortable because it serves several parties at once. The programme manager gains a breathing space: a green status buys another month without scrutiny. The sponsor gains the ability to tell their own superiors that the programme is under control. The board gains the sense that it has discharged its duty of oversight simply by having met and read the pack. Everyone leaves the room a little reassured, and the reassurance is mistaken for knowledge.
The pattern that recurs across complex programmes is that this comfort is most complete precisely when it is least warranted. A programme in genuine health can afford candour; its problems are ordinary and its trajectory sound. A programme in trouble cannot. The incentives to present difficulty as manageable, and manageable difficulty as resolved, grow stronger exactly as the underlying reality deteriorates. By the time the report finally turns amber, the amber is not an early warning — it is a confession that could no longer be delayed.
Why Reporting Crowds Out Insight
If the problem were simply dishonesty, it would be tractable; one would replace the dishonest people. But the more troubling truth is that reporting crowds out insight even when everyone is honest. Several structural forces produce this result, and they operate whether or not anyone intends them to.
- Cadence. Reporting runs to a calendar — weekly, fortnightly, monthly. Insight arrives on its own timetable, often between reporting cycles and rarely in time for the pack. A rhythm designed for administrative regularity is a poor instrument for catching irregular truths.
- Format. The template that makes reports comparable across a portfolio also strips out the particular. A RAG rating, a milestone count and a short narrative box can capture status; they cannot easily hold the tangled, conditional, half-formed understanding that constitutes real insight.
- Aggregation. Every layer a report passes through smooths it. The team lead rounds up to spare the programme manager; the programme manager rounds up to spare the sponsor. No single act is a lie, but the cumulative effect is that bad news loses a shade of its colour at every hand-off.
- Audience. A report written for a senior audience with fifteen minutes and a dozen programmes to consider must be brief, and brevity is the enemy of nuance. The very courtesy of not wasting a director’s time removes the detail in which the real story lives.
- Consequence. Where a poor status invites intervention, and intervention is experienced as interference, the rational compiler learns to keep the status good enough to be left alone. The report becomes a shield rather than a signal.
Each of these forces is individually reasonable. Together they ensure that the report drifts steadily away from the reality it is meant to describe, and that the drift is always in the same direction — towards comfort.
The Inversion of Measurement
Beneath these forces lies a subtler one: the things easiest to measure are rarely the things that matter most, and measurement systems reward what they can count. A programme is asked how many milestones it has hit, how much of its budget it has spent, how its earned value compares to plan. These are answerable questions, and their answers fill the report. But they describe motion, not progress, and the two can diverge for a long time before the divergence surfaces.
| The report tends to measure | Insight would ask about |
|---|---|
| Milestones passed | Whether the milestones still mean what they meant when set |
| Budget consumed against plan | Whether the plan was ever a credible model of the work |
| Deliverables produced | Whether anyone is using them, or can |
| RAG status this period | What changed this period, and what it implies |
| Risks logged and rated | Which risk no one has yet dared to write down |
The inversion is that the measures crowd out the questions. A programme can pass every milestone on its schedule and still be failing, because the milestones were the wrong ones, or because passing them has quietly consumed the goodwill and the slack the later stages will need. Earned value analysis, applied well, is a genuine advance on naive spend-tracking; applied as a reporting ornament, it lends a spurious precision to a plan whose foundations were never sound. The number reassures in proportion to its decimal places, not its truth.
The most dangerous consequence is that the act of measuring changes what is measured. When a RAG rating carries real weight — when green means autonomy and red means the loss of it — the rating stops describing the programme and starts defending it. Colour becomes politics. This is not corruption; it is the predictable response of intelligent people to a system that punishes candour.
The Deeper Force: Information Asymmetry
We reach, then, the structural root. The people who know most about a programme’s true condition are the people doing the work, and the people who most need that knowledge are the people overseeing it. Between the two sits an asymmetry of information that no reporting template dissolves. Those closest to the work know its real state; those accountable for it depend on what the first group chooses, and is able, to tell them.
This is the classic shape of the principal and the agent. The board is the principal; it wants a true account. The delivery layer is the agent; it possesses the true account but is not neutral about how it is received. The agent’s interests are not identical to the principal’s — job security, professional reputation, the wish to solve a problem before it must be disclosed, all pull towards optimism. The reporting system is the channel through which the principal tries to see past this, and it is a channel the agent largely controls.
“A programme’s reporting is only ever as honest as it is safe to be honest, and safety is set by the principal, not the agent.”
Understood this way, the gap between reporting and insight is not a failure of the reporting system so much as its natural equilibrium. As long as the flow of information is controlled by the party with an interest in how it lands, and as long as candour carries a cost, the system will settle at a level of honesty that is comfortable rather than complete. The astonishing thing is not that programmes are optimistically reported. It is that we expect anything else from an arrangement built this way.
What Insight Actually Requires
If reporting produces reassurance, what produces insight? Not a better template — the belief that the right form will finally extract the truth is the oldest illusion in programme management. Insight requires conditions the standard reporting relationship does not supply.
It requires, first, safety: an environment in which telling the truth about difficulty is rewarded rather than punished, or at least not punished. A sponsor who greets amber with curiosity rather than displeasure will learn things a sponsor who greets it with displeasure never will. The quality of the information a leader receives is set largely by how they have reacted to bad information in the past.
It requires, second, proximity. Insight lives in the detail, and detail does not survive aggregation. Leaders who rely solely on the summarised pack have chosen to see the programme only through the very filter most likely to mislead them. The remedy is not to abolish the pack but to supplement it — to spend time close enough to the work that the summary can be tested against something.
It requires, third, the right questions. A report answers the questions its template asks. Insight comes from the questions the template omits: not are we on track? but on track to what, and do we still believe in the destination?; not what is the status? but what do you know now that you did not know a month ago? These are not questions a form can pose. They require a person willing to ask, and to listen to an inconvenient answer.
Reforming the Reporting Relationship
None of this argues for abolishing reports. A portfolio of programmes needs a common instrument, and the status report, for all its faults, is that instrument. The argument is for demoting the report from an oracle to what it is — a useful, partial, systematically biased signal — and for building around it the conditions in which insight can also travel. In my experience the following shifts do more than any template revision.
- Change how bad news is received before changing how it is reported. The reporting will not improve until it is safe for it to improve. A leader who wants honest amber must make amber survivable. This is the first move because every other move depends on it.
- Read the report as an artefact, not a window. Ask always who wrote it, for whom, and under what incentive. A green status from a team that has learned green buys autonomy is not the same signal as green from a team that has learned candour is safe. The rating means little without the relationship behind it.
- Separate the cadence of reporting from the cadence of understanding. Keep the monthly pack for administration, but create channels — a standing conversation, an open escalation route, a habit of walking the work — through which insight can arrive when it arises, not when the calendar permits.
- Prize the risk no one has written down. The most valuable item in any programme is the concern that is felt but unrecorded, because recording it feels premature or disloyal. A leader who can make it safe to voice the unwritten risk has done more for their oversight than any dashboard.
- Judge the reporter by their surprises. Over time, the test of a reliable source is not how green their reports are but how rarely they are caught out. A team whose reports are modest but never surprised is worth more than one whose reports are confident and periodically catastrophic.
These are relational reforms, not technical ones, and that is the point. The gap between reporting and insight is a gap in a relationship — between principal and agent, overseer and doer — and it closes, when it closes at all, through the patient work of making truth cheaper to tell than to hide.
The Programme That Knows Itself
The programmes that come closest to closing the gap are not those with the most elaborate reporting. They are those in which the people accountable have made it worth someone’s while to tell them the truth, and have proven, repeatedly, that they can be trusted with it. Their reports look much like anyone else’s. What differs is everything around the report — the tone in the room when the status is discussed, the fate of the last person who raised a real problem, the number of questions asked that the template did not require.
Reporting will always tend towards reassurance, because that is what the instrument is built to produce and what its audience, at some level, wants. Insight will always be harder, because it asks its audience to hear what they would rather not. A practitioner cannot repeal these forces. But they can refuse to mistake the one for the other, and in that refusal lies most of the difference between a programme that is well reported and a programme that is actually understood.