By Paulius Petravicius

Fictional teaching scenario: Maya is polishing a green SteerCo slide. The booking-service trial looks reassuring: workshops completed, supplier meetings held, testing “progressing”. Meanwhile, the RAID log shows a blocking interface issue, and the forecast finish moved last Tuesday.

Nobody has asked Maya to lie. The sponsor wants confidence. The team hopes the fix will land before Friday. Changing the colour would mean explaining why last week’s confidence has evaporated. Green feels like the least disruptive choice.

This is watermelon reporting: green on the outside, red on the inside. A watermelon project status appears healthy while the evidence underneath says something else. The verbal version is “we’re fine” followed by six conditions that must miraculously resolve themselves.

The problem often grows from safety and incentives: what happens to the person who brings unwelcome news? The fix combines evidence rules that survive optimism with a culture that makes red and amber safe, useful signals. A better spreadsheet helps. It cannot chair the meeting for you.

Definitions: what are we looking at?

Watermelon reporting: common PMO slang for a reassuring status that conflicts with adverse delivery evidence; it is not a certified term.

RAG: Red, Amber and Green, used to summarise project health or delivery confidence against agreed expectations.

Declared versus computed status: the assessment shown in the report versus the result of applying the agreed scorecard rules to evidence.

Road to green: the cause, corrective action, owner, date and decision needed to restore a supported position.

Manage by exception: delegate within agreed tolerances and escalate when a breach is forecast, rather than waiting for it to happen.

Education note: the detection table, checklist and make-red-safe playbook below are InsightSpotter teaching aids for local adaptation, not official PMI, PeopleCert or ISO anti-pattern standards. Organisations define their own RAG meanings, escalation paths and reporting habits.

Why watermelon reporting happens

Maya’s first problem is the reporting rhythm. The slide is assembled before the forecast is challenged, and the colour is negotiated before the issue is understood. By the time the evidence arrives, Green already has a constituency.

Fear reinforces that rhythm. If early Red brings public interrogation, reporters learn to delay it until the facts are undeniable. Sponsors may sincerely request transparency while rewarding people who never need help. The lesson comes from their reaction to bad news, not the transparency slogan.

Hope supplies the next ingredient. A supplier promises a fix, so the team reports the future it wants instead of the forecast it can support. One more cycle feels harmless. Then the recovery window closes while the slides remain beautifully consistent.

Activity also impersonates progress. Meetings happened, tickets moved and people worked hard. Those facts matter, but they do not establish that the required outcome will arrive on time. A tidy delivery board cannot, by itself, establish project readiness, benefits or external dependency health.

Finally, missing rules leave room for negotiation. Without explicit thresholds, Green can mean “no disaster yet”, “within tolerance” or “please don’t ask”. An override without an expiry becomes permanent. Silence becomes assumed agreement. Missing evidence quietly inherits last week’s Green.

Watermelon project status: eight warning signs

This is an InsightSpotter teaching aid, not a diagnostic score or proof of misconduct. One sign starts a conversation; it does not convict a project manager. Consistent Green may be entirely deserved when current evidence supports it.

Smell test	What to check before accepting the colour
Every workstream is permanently Green	Ask for current evidence and changed forecasts; distinguish genuine stability from copied status.
“Risks: none” survives every review	Check dependencies, assumptions and residual exposure with the people doing the work.
The update lists activity, not outcomes	Ask what is accepted, what remains and whether the delivery forecast changed.
Red facts sit under a Green summary	Reconcile the failed check, blocking issue or forecast breach with the agreed rule.
Overdue RAID actions disappear from the pack	Trace their IDs, impact and next response; overdue administration alone does not set the project colour.
“Monitor closely” is the whole recovery plan	Identify an action that changes the position, an owner and a decision deadline.
Declared and computed status differ without a record	Find the reason, approver, approval evidence and expiry cycle.
No update is treated as good news	Check evidence dates and completeness instead of carrying Green forward automatically.

Ask “Which fact supports this?” before “Who made this Green?” The first question invites investigation. The second can make the next report even less informative.

The cost is the decision you can no longer make

Hidden trouble consumes options. A dependency raised early might allow resequencing, a smaller trial or a different supplier commitment. Raised late, it may leave only an expensive delay.

Trust suffers too. Once a sponsor discovers that the summary contradicts the working records, every later colour needs extra explanation. Reporting becomes heavier precisely because earlier reporting was too comfortable.

An exception then arrives as a shock. People spend the meeting debating when someone knew, instead of choosing a response. Recovery turns into political theatre, with the fruit taking the blame for a governance problem.

Make red safe, then make it useful

The following InsightSpotter teaching playbook combines reporting discipline with sponsor behaviour. Adapt it to existing authority and controls; it does not introduce a new governance standard.

1. Agree meanings before choosing colours

Use the RAG status criteria guide to agree dimensions, evidence and explicit Green, Amber and Red meanings. Its scorecard is an educational method for local adaptation, not a universal scoring law.

Discuss difficult cases before the pack is due: an incomplete forecast, an accepted high risk, a failed mandatory check. Agreement under pressure is much easier when the rules already exist. Keep the detailed thresholds on the criteria page rather than inventing a second set here.

2. Put computed and declared status side by side

Show both when they differ. Record the cycle, factual reason, named approver and role, approval evidence and date, and the cycle when the override expires unless renewed. Readers should see the judgement being exercised.

An override cannot complete missing evidence or close an unresolved adverse fact. Under the linked method, an unsupported required assessment is Not assessed; an independently established Red exception still takes precedence. Known adverse facts remain visible even when current evidence is stale. A blank field is not a quiet Green.

3. Give non-green a road to green

For Amber or Red, record the cause, action, owner, date and ask. “Monitor closely” describes attention; it does not change a forecast. A useful action might secure an environment, resolve a defect or obtain an authorised scope decision.

For Not assessed, name the evidence gap, who will resolve it and by when. For a failed acceptance check, state what evidence will satisfy closure. You can publish an honest problem before every recovery detail is known; identify the immediate containment or investigation and when options will be ready. Urgent escalation should not wait for a perfect plan.

4. Change the sponsor’s first response

Try: “Thank you for raising this. What is affected, how soon must we decide, and what help do you need?” Challenge evidence firmly while keeping the reporter safe from humiliation. Accountability includes following through on the response.

AWS OPS03-BP03, “Escalation is encouraged”, explicitly supports early escalation and protection from reprimand. Its context is operational excellence; the useful project-reporting lesson is to pair permission to speak with a working escalation route.

5. Connect the colour to a decision trail

Link the status statement to the relevant issue, risk, acceptance result and forecast. The RAID log template guide helps keep those records distinct and traceable. Closing a decision record does not close the delivery issue it addresses.

APM’s governance overview connects delegated authority, escalation routes and reporting. Apply that distinction: who can act now, and which choice needs authority elsewhere? A Red label alone does not answer either question.

PeopleCert’s PRINCE2 7 issues guidance encourages early issue capture and explains that not every issue is a change. Similarly, do not translate every Red into an automatic Exception Report. In a PRINCE2 setting, follow the agreed tolerances, forecast breach and escalation responsibilities; a locally chosen colour is not itself the formal trigger.

6. Build a rhythm that catches contradictions

Before each pack, reconcile the forecast, open exceptions and declared status with their owners. Between packs, act on urgent triggers immediately. At the meeting, protect time for decisions; afterwards, record the choice, owner and next review.

The RAG status calculator companion provides a reviewable worksheet workflow for carrying evidence into a colour. It is not a probability of success or permission to proceed. Use it to expose disagreement while there is still time to act.

Worked mini-case: the same trial, a more honest conversation

Fictional teaching example: this extends the booking-service shape used in the RAID guide. The weeks, evidence and outcome below illustrate reporting choices; they are not a client case or a claim about live delivery.

Week N: thin evidence, reassuring summary. Maya’s pack declares Green because the team expects to recover. ISS-001 records a failing booking-confirmation interface. The finish forecast has slipped, but the report offers only completed workshops and a supplier promise. The colour has outrun its evidence.

At review, the team establishes that the failed integration test is a required mandatory acceptance check. Under the linked RAG method, that open failure is Red. If the current cost forecast is also unavailable, show the evidence gap alongside Red; do not downgrade the known failure to uncertainty.

Week N+1: honest Red, specific response. The status reads: “Red — mandatory booking-confirmation acceptance check remains failed; wider trial readiness cannot be confirmed.” The road to green names Noor to fix and retest the interface by the agreed review date, with a passed result reviewed by the technical lead as closure evidence. Maya owns the missing cost forecast update.

The SteerCo ask compares a later wider trial with a restricted staff-only trial, subject to safety, acceptance and operational checks. It names the authorised decision maker, decision deadline and consequence of deferral. Use the decision-first SteerCo agenda to give that choice protected time.

Suppose the sponsor approves preparing the staff-only option. Record the scope decision separately, then update implementation actions and any approved baseline. That approval does not pass the failed test. Keep the failure visible until authorised closure requirements are satisfied, and recompute status from the resulting evidence.

The immediate improvement is a decision people can act on. The project has not become healthier merely because the reporting has become more honest.

Choose the lightest honesty check that works

Use this InsightSpotter teaching checklist before accepting the next status. It is a conversation guide, not a maturity score.

• Are the colour meanings and material dimensions agreed before this reporting cycle?
• Does the report show forecasts as well as completed activity and actuals?
• Can a reader trace material claims to dated evidence and an owner?
• Are open issues, residual risks and failed checks visible through their record IDs?
• Is missing evidence explicit, with retained adverse exceptions still shown?
• If declared status differs, is the override approved, evidenced and time-limited?
• Does non-green have an action, owner, date and clear ask where a decision is needed?
• What happened the last time someone raised Red early: practical help or public punishment?

Start where the answers expose a real weakness. If the team lacks a safe escalation route, adding three more tabs will mainly give fear somewhere else to hide.

When not to over-correct

A tiny internal task with continuous contact may need a shared action list and a direct conversation, rather than a weekly colour ceremony. Keep mandatory controls, but scale the reporting effort to the decisions and exposure.

Amber also needs room to be useful. Turning every Amber into a crisis meeting encourages people to avoid it. Agree what the team can handle within authority and what needs help. Red can be honest and useful; it is not automatically evidence of failure.

Nor should Red become a weapon for stopping work without explaining the constraint or the options. Separate a genuine safety or acceptance stop from a decision request, and make the route forward clear. Ask for evidence whichever colour someone prefers.

For Maya, the next good-news slide can wait until the evidence supports it. The useful news today is that the sponsor can still make a choice. That is a better reporting habit than keeping the fruit bowl permanently green.

If you would like more practical ways to turn project evidence into clearer decisions, subscribe to the InsightSpotter newsletter.