Status Reporting
Meera's first weekly update to Lakshmi is a list of fourteen ticket numbers and the words "going well". Lakshmi replies with one question: "Will it launch on the 14th?" The update was long, and it still didn't answer the only question its reader had.
The rule
Lead with the verdict; then what changed, what's at risk, what you need.
Readers skim. A status report works if a busy person can act on it in under a minute, and that calls for a fixed order:
- The verdict. On track, at risk or off track. Agree what the words mean: for example, at risk means the date could slip unless something changes, and off track means it will slip.
- What changed. Progress in outcomes ("mandate screens finished and tested"), not activity ("worked on screens").
- What's at risk. Each risk with its impact on the date and what is being done about it.
- What you need. Specific asks, each with a person and a date.
Two more habits help. Be honest early. A project that reports "on track" for weeks and then suddenly misses is sometimes called a watermelon: green on the outside, red inside. It destroys trust faster than any honest "at risk". And keep the format the same every week, so readers know exactly where to look.
Here is Meera's rewritten update:
UPI autopay: week 4 of 6
Status: AT RISK (last week: on track)
Changed: Mandate screens finished and tested on Android and iOS.
Webhook handling about 70% done.
Risk: The bank's sandbox is still unavailable. A mock keeps work
moving, but real testing needs 4 days once it is up. If it
isn't live by Wednesday, launch moves from the 14th to the 18th.
Ask: Lakshmi, please raise sandbox access with the bank's partner
manager by Tuesday.The shortcut
Apply the 30-second test: could a busy reader find the state, the biggest risk and your ask within 30 seconds? If not, move those three to the top and cut the rest.
Find the verdict
Is the 14th safe? Not unless the sandbox arrives, so the verdict is "at risk".
Drills
Answer fast — trust the rule.
What should the first line of a status update say?
A project reported "on track" for weeks, then suddenly missed its date. What went wrong?
Which line reports progress best?
Which is a well-formed ask?
Remember
- Lead with the verdict; then what changed, what's at risk, what you need.
- The 30-second test: the state, the biggest risk and the ask must be findable at a glance.
- Report "at risk" early; a watermelon status destroys trust.