Status Updates and Bad News
For five weeks the weekly update to Meera said "On track". Then, in week six, the change advisory board moved its meeting past the planned go-live date. How you report that one fact decides whether Meera trusts every update that follows.
The rule
Say where it stands, what's at risk and what you need — early.
A useful status update keeps the same shape every week:
Status: At risk. Go-live may slip from the 16th to the 19th.
Done: 8 of 10 carriers live; 1,900 invoices checked automatically.
Next: carriers 9 and 10; clerk training on Thursday.
Risk: the change board moved to the 18th, after our date. Owner: Kavitha.
Decision needed by Wednesday: accept the 19th, or ask for an emergency slot?- Where it stands: one honest status, such as on track, at risk or off track, and the reason.
- What's at risk: each risk with an owner, not a vague worry.
- What you need: decisions, with the date they are needed by.
- Early: bad news loses value every day it waits. Told early, it leaves options; told late, it leaves only apologies.
Beware watermelon reporting: green on the outside, red inside. Reporting "on track" for weeks while problems grow, then turning red in the final week, destroys trust faster than any slip.
Speak the reader's language. Farhan does not need "the confidence threshold was raised to 0.9". He needs "about 40 more invoices a day will come to your team, because the system now approves on its own only when it is very sure."
Match the channel to the news, too. Serious bad news goes by a call first, then in writing with the same facts.
The shortcut
Apply the headline test: if the reader sees only the first line, do they know whether to worry?
The fact
The change board now meets on the 18th. The planned go-live was the 16th.
Drills
Answer fast — trust the rule.
What is "watermelon reporting"?
When should Meera hear about a likely slip?
Which line should open a weekly update?
How should you tell Farhan that the confidence threshold was raised to 0.9?
What is the best way to deliver serious bad news to the sponsor?
Remember
- Say where it stands, what's at risk and what you need — early.
- Shortcut: the headline test. Does the first line tell the reader whether to worry?
- Trap: watermelon reporting, jargon, and bad news buried deep in an email.