The Watermelon Effect: Why Projects Report Green While They Turn Red

In brief

The watermelon effect is a project that reports green while the work underneath has turned red. Why teams underreport, what it costs, when to go red, and how to raise bad news without losing standing.

What is the watermelon effect in project management?

The watermelon effect describes a project whose reported status is green on the outside while the work underneath has already turned red. The status report says the project is healthy. The schedule, budget, or scope says otherwise. The gap between the two stays hidden until it is too large to hide.

Why do teams keep reporting green?

Teams rarely set out to mislead anyone. They report green because of the pressure to stay positive. I call this the Transparency Trap: the more an organization says it values openness, the more a red status can feel like a personal risk to the person who reports it.

In my research and in two decades of practice, I see the same pattern. Teams that never learn to handle conflict, or learn it too late, tend to underreport red status. The report stays green because turning it red means having an uncomfortable conversation they believe is coming and would rather put off.

What does it cost?

Status holds green long after the work has gone red, so the gap widens unseen and the correction arrives as a shock. By then, the options that were available early (more time, less scope, added help) are usually gone. The sponsor loses trust in the project, and in every report that came before.

Project timeline Reported status: green Actual health The gap nobody sees Escalation lands here, as a surprise Healthy Failing
The watermelon effect. Status holds green long after the work has gone red, so the gap widens unseen and the correction arrives as a shock. Escalating earlier trades a small, survivable surprise for a large one.

When should a project manager go red?

Earlier than feels comfortable. Escalating early trades a small, survivable surprise for a large one. I give project managers two guides.

First, trust yourself. If something feels off, it’s time to have a conversation. You don’t need proof to start one.

Second, let your metrics be your guide. Watch your cost performance index (CPI) and schedule performance index (SPI). If they’re edging toward your project’s thresholds, that’s a signal something is amiss and worth raising now.

How do you raise bad news without losing standing?

Start before there is any bad news. At the beginning of the project, set expectations with your sponsor and team for how you will talk about status and changes in status. Agreeing on the rules of engagement up front makes the hard conversation easier if and when it comes.

Then, when bad news needs to be communicated, do it swiftly and with as much information as you have. You usually can’t wait for the complete picture. A prompt, partial report gives people time to act. A complete one that arrives late does not.

About the author. Douglass P. Smith, Ph.D., PMP, is Professor of the Practice in project management at the University of Kansas and a licensed minister in Kansas City, Kansas. More about Dr. Smith.

Drawn from ongoing research on escalation and status reporting. See speaking topics and engagements.

← All writing