The status update that said nothing. A small autopsy.

A friend forwarded me a status update last week. He had received it from a programme he was sponsoring, and he wanted my read on whether the programme was in trouble.

I read it three times. I genuinely could not tell.

That, I told him, is the answer.

The actual update

Here it is, lightly disguised, in full:

We continued to make progress on the Atlas integration this week. The team is working closely with downstream stakeholders to align on the path forward. We are re-prioritising the remaining backlog in light of feedback from the recent steering. The ETA is still tracking to Q3. Vendor discussions are ongoing and we are working to find a solution that works for all parties. We will share a more detailed update at next month’s review.

Six sentences. Roughly one paragraph. A confident, professional tone. And, on close reading, no information at all.

The four sentences I’d cross out

“Continued to make progress.” Translation: nothing finished this week. If anything had finished, it would be named in the same sentence. Specific finishes are the only proof of motion.

“Re-prioritising the remaining backlog.” Translation: something just slipped. Healthy programmes don’t need to re-prioritise weekly. The phrase is the linguistic equivalent of cleaning the desk before an inspection.

“ETA still tracking to Q3.” Translation: the ETA is wobbling. People only feel the need to reassure you about an ETA when the ETA has started to soften. A clean ETA gets reported by date, not by reassurance.

“Vendor discussions are ongoing. Finding a solution that works for all parties.” Translation: someone said no. A specific decision is blocking the programme, and the writer doesn’t have the authority to break it, doesn’t have the relationship to escalate it, or doesn’t want to name it on a public status thread. All three are equally important to know.

What an honest version would look like

Same six sentences, written for someone who can actually help:

This week we finished the Atlas auth-handshake (was scheduled for last week). We did not finish the rollback playbook (was scheduled for this week). It now moves to next week, with no new dependencies. ETA Q3 is now soft. My best read is week 38 ± 2 weeks. The vendor SLA negotiation is stuck. The legal team has flagged the indemnity clause. I need a 30-min call with the GC by Friday to resolve. Everything else green.

This is the same six sentences. It takes longer to write. It is harder to defend in a meeting. It is also the version that lets the sponsor help.

The test I use now

When I write a status update, I delete it and try to remember what I just said.

If the deleted version doesn’t read like a meaningful loss to anyone, if the sponsor can’t tell the difference between “I sent the update” and “I forgot to send the update”, then the update was furniture. It existed. It did not communicate.

The mark of a good status update is that someone, somewhere, does something differently because of it.

The autopsy of a bad one is that nobody could.