Watermelon Reporting

Why Project Status Hides the Truth — and What to Do About It

Every organisation has it.

A project looks green on the outside. Cut it open and it is red all the way through.

The status report says "all okay." The PowerPoint is calm. The RAG dashboard glows reassuringly. And the team doing the actual work is barely holding things together.

This is watermelon reporting — green on the outside, red in the middle — and it is one of the most reliably damaging communication failures in organisational life. Not because people are dishonest, but because honesty has been made to feel unsafe.

Why project status hides the truth — and what to do about it

RAG status reporting — Red, Amber, Green — is the most common shortcut for communicating project health. It is also one of the most unreliable.

The problem is not the colours themselves. The problem is that RAG is almost always subjective. It is easy to game, easy to interpret generously, and easy to shade toward the optimistic end of the spectrum when the culture around you treats Red as a punishment rather than information.

In those environments, people do not lie out of malice — they shade the truth out of self-preservation. They mark Amber hoping they can recover before anyone notices. They delay the bad news. They protect themselves from consequences that should never have been attached to honest reporting in the first place.

The PowerPoint says everything is green. The team is barely holding it together. Both things are true simultaneously, in organisations everywhere.

W. Edwards Deming put it precisely:

without data, you are just another person with an opinion.

Most RAG status reporting is exactly that — opinion. Optimism disguised as confidence. Hope standing in for evidence. Leaders are told what they want to hear rather than what they need to know.

This is watermelon reporting. And it seeds false hope, distorts timelines, and causes decisions to be made on the basis of a reality that does not exist.

Why it happens — and why it persists

Watermelon reporting does not thrive because people are fundamentally dishonest. It thrives because honesty feels genuinely unsafe.

In organisations where Red is treated as failure — where the person who raises the problem becomes the problem — people learn quickly that the rational move is to shade toward green and hope the situation resolves itself before it becomes unavoidable. This is not a failure of character. It is a rational response to a dysfunctional incentive structure.

It shows up everywhere. The official leadership update. The status report in the work tracking tool. The ad-hoc hallway conversation — "everything is going well!" The spreadsheet modified to show green. The Excel dashboard with numbers that reflect what was hoped for rather than what happened. It is endemic across industries, organisation sizes, and management cultures.

There is also a human optimism problem. People genuinely believe they will be able to recover the situation before anyone needs to know about it. Sometimes they are right. More often, the delay only compounds the cost — because problems that could have been addressed with a small intervention at week three become crisis-level failures at week twelve, precisely because nobody raised the flag.

What to do about it

The antidote to watermelon reporting is not a better reporting system. It is proximity to reality, and a culture in which Red is treated as a request for help rather than an opportunity for blame.

Practically, this means several things.

Demand evidence behind the colour.

If you are using RAG status, require teams to state what observable evidence supports the colour they have chosen. What has been delivered? What has been measured? What is the data showing? This shifts the conversation from subjective impression to observable fact — and makes it significantly harder to sustain an optimistic green when the evidence tells a different story.

Get closer to the work.

Dashboards and status reports are abstractions. Go and see what is actually happening. Talk to the people doing the work, not just the people reporting on it. Visit the team. Look at what has been built. Ask what is genuinely difficult. The closer you are to the reality of the work, the less effective watermelon reporting becomes as a strategy.

Connect investment, activity, and outcomes explicitly.

Most watermelon reporting is possible because nobody has connected the dots between what was invested, what work has happened, and what value has been produced. When those three things are tracked together and visible, the gap between the optimistic status and the actual reality becomes much harder to sustain.

Build a culture where Red means support.

This is the most important and the hardest. If the consequence of raising a red flag is being blamed, criticised, or penalised — people will not raise it. If the consequence is being supported, resourced, and helped to recover — people will raise it early, when it can still make a difference.

Leaders who genuinely want honest reporting have to demonstrate, repeatedly and consistently, that honesty is not punished. And they have to notice when it is — even subtly — and stop it.

Consider abandoning RAG entirely for high-stakes work.

The original design intent of RAG status — a quick summary of project health — is reasonable. But the execution almost always produces watermelon reporting in cultures with any performance pressure at all.

Better alternatives anchor reporting to specific deliverables, actual metrics from the work tracking tool, and real-time data feeds that cannot be manually adjusted. The more the reporting is connected to observable reality rather than human interpretation, the harder it is to game.

Why this matters

Decisions are only as good as the reality they are based on.

Watermelon reporting delays action, burns trust, and wastes money and energy on false confidence in plans that have already quietly failed. The cost of discovering the truth late is almost always greater than the cost of discovering it early — and the gap between the two is almost always created by a culture that made honesty feel more dangerous than silence.

Truth, even when uncomfortable, gives leaders something solid to work with. The Stoics understood this: the truth itself never hurt anyone. Avoiding it always does eventually.

Clarity begins where pretending ends.