RAG Status Reporting That Executives Actually Trust (‘Red Means Red’)
Every failed project we have ever been called to rescue had one thing in common: a stack of green status reports. The project was drowning, and the reporting said swimming. There is even a name for it, the watermelon project: green on the outside, red on the inside. Fixing that is not a template problem; it is a governance and culture problem, and it sits at the heart of our delivery governance practice.
Why reporting goes watermelon
Nobody sets out to lie to a steering committee. The rot is structural:
- Optimism is rewarded, honesty is punished. If the first Amber triggers an interrogation and the messenger gets blamed, every rational project manager reports Green until the truth is undeniable, which is always too late. This dynamic is one of the failure patterns we unpacked in why IT projects fail.
- No agreed definitions. If Green, Amber and Red have no criteria, they mean “mood of the PM this Friday”. One person’s Amber is another’s Red.
- Status by negotiation. When vendors or workstream leads can argue their colour upward in the pre-meeting, the report reflects politics, not position.
- Too much data, no signal. A forty-slide deck hides problems better than it reveals them. Executives skim; the one number that mattered was on slide 31.
The rules that make RAG mean something
1. Define the colours in writing, against the baseline. Green: on track against the approved baseline, no intervention needed. Amber: deviation exists or is imminent; the team has a credible recovery plan within its own authority. Red: baseline will be missed; a decision above the project’s authority is required. Note what Red is not: a moral judgement. It is a request for a decision.
2. Red must trigger help, not blame. The steering committee’s response to a first Red defines the culture for the rest of the programme. If Red reliably produces decisions (resources, descoping, deadline movement), Reds will arrive early, while they are cheap. If it produces a witch hunt, you have bought yourself green watermelons until go-live collapses.
3. One page. Every week. Same structure. Executive summary first, overall RAG with trend arrow, then the exceptions: what changed, decisions needed (with a date), top risks with owners, milestones against baseline. If everything cannot fit on one page, the project doesn’t have a reporting problem; it has a clarity problem.
4. Trend beats snapshot. A project Amber for six consecutive weeks with no movement is a Red wearing camouflage. Always show last week’s colour beside this week’s. Direction of travel is the most honest indicator a report can carry.
5. Status is derived, not negotiated. The colour follows from the definitions and the data: milestone variance, unresolved dependencies, open critical defects. It is announced, explained and evidenced, not bargained in a corridor.
6. The PM owns the words. Status written by committee converges on comfortable. One accountable author, one honest voice, reviewed for accuracy, not for tone.
What executives should demand
If you sit on a steering committee, three questions expose more than any dashboard:
- “What would have to be true for this to be Red?” If the answer is vague, the definitions don’t exist.
- “What decision do you need from us today?” A healthy project usually needs one; a report with never any asks is decorative.
- “What got worse since last time?” Every real project has something. “Nothing” is not reassurance; it is a flag.
Honest reporting is a rescue-prevention system
In our project rescue work, re-establishing truthful reporting is always the first repair, because every other fix depends on it. The cheaper option is not to lose it in the first place. Right-sized governance, written colour definitions, one-page reporting and a steering culture where Red means “decide”, not “blame”: that is most of the machinery, and it costs almost nothing to run.
We set this up as part of our IT project management services: governance that fits the project, reporting executives can trust, and a standing rule we bring to every engagement: Red means Red.
Frequently Asked Questions
What does RAG status mean in project management?
Red, Amber, Green: a traffic-light summary of project health against the approved baseline. Green means on track, Amber means a deviation with a credible recovery plan, Red means a decision above the project’s authority is required.
What is a watermelon project?
A project that reports Green on the outside while being Red on the inside. It usually signals a reporting culture where honesty is punished and optimism is rewarded.
How do you make RAG reporting trustworthy?
Define the colours in writing against the baseline, derive status from data instead of negotiation, keep the report to one page every week, always show the trend beside the snapshot, and make Red trigger help rather than blame.
What should executives ask in a steering committee?
Three questions expose more than any dashboard: What would have to be true for this to be Red? What decision do you need from us today? What got worse since last time?
Editorial note — This article was researched and drafted with the assistance of Claude (Anthropic), and reviewed and approved by Amazing Projects before publication.
