Draft — needs reviewStatus: draft
Guide
Watermelon reporting and how to stop it
Short answer
Watermelon reporting is when a project shows green on the outside while it is red inside. Stop it with one written health rule applied to plan data, unassessed work shown as no data instead of green, health reported as “N of M projects on track”, and the decision each red needs written next to it.
What watermelon reporting is, and why it survives
[Draft: to be written by SprintPM Field Notes.]
Why self-reported RAG drifts towards green
[Draft: to be written by SprintPM Field Notes.]
Rule 1: one health rule, applied to plan data
[Draft: to be written by SprintPM Field Notes.]
Rule 2: no default green; unassessed is “no data”
[Draft: to be written by SprintPM Field Notes.]
Rule 3: report counts, never a blended score
[Draft: to be written by SprintPM Field Notes.]
Rule 4: every red names the decision it needs
[Draft: to be written by SprintPM Field Notes.]
How to introduce the rules without a fight
[Draft: to be written by SprintPM Field Notes.]