Your Status Update Is Too Long and Nobody Read It

I used to spend an hour and a half every Thursday evening on a weekly status report, and I was quietly proud of it. It was thorough. It was well structured. And for three weeks running I buried a request for a decision in the third section and nobody answered it, because nobody got that far. I found out when the thing I needed the decision about became a problem, and my sponsor said, honestly and without malice, "you should have told me."

Somewhere early in most technical careers we absorb the idea that the volume of a report signals the seriousness of the work. Long report, hard week. Short report, what have you been doing.

Your readers have the opposite instinct, and they're right. When a senior person opens a 900 word update, the first thing they feel is not "how thorough". It's "what is being hidden in here". Length reads as hedging. It reads as someone who hasn't worked out what matters and is covering themselves by including everything, which, if you're honest about the Thursday evenings, is quite often what it is.

There's a harder version of this too. A long report lets you avoid saying the thing. You can write eleven bullets about progress and mention the eight week hardware slip in bullet nine, and technically you told them. Technically. That's the move that ends careers, and the worst part is that it rarely feels like dishonesty at the time. It feels like completeness.

Assume your reader gets two lines on a phone, in a corridor, between meetings. Everything else is there for the people who want detail, and that's a smaller group than you think.

So the first line says where you are against the thing they care about, with a number. The second line says what you need from them, with a name and a date. That's it. If those two lines are right, the rest of the document can be as long as you like, because it's now reference material rather than a test of the reader's stamina.

Notice what isn't in the first two lines. Not what the team worked on. Not how hard it was. Not the list of meetings held. Effort is not a status. Nobody has ever made a decision on the basis of how busy you were.

While we're being honest about status reports, let's talk about the colour.

Green means the date and the scope hold. Red means they don't. Amber, in practice, means "something is wrong and I'd rather not have the conversation about it yet." I've used it that way. Most people reading this have used it that way.

Here's the problem. Amber buys you two weeks of peace and costs you every bit of credibility you had when it turns red, because the first question will be "when did you know?" and the true answer is always "a while ago". Whereas a red raised early, with a recommendation attached, makes you look like someone who is in control of their project. Same news, completely different read on you, purely as a function of timing.

If you use amber, define it. Put a sentence next to it saying exactly what would take it back to green and by when. An amber with no exit condition is a hope, not a status.

A network refresh for a cruise line. Eleven ships, new switching and wireless, fitted during dry dock and turnaround windows across fourteen months. Here's the shape of the update the lead was sending, paraphrased and shortened, because the real one was longer:

"This week the team completed the deck surveys on the first two ships and made good progress on the configuration templates. We held the weekly design review on Tuesday and worked through several outstanding queries with the vendor regarding the wireless controller licensing model. The logistics workstream has continued to engage with the supplier on delivery scheduling. There are some open questions around the timing of hardware arriving for the second tranche which we are working through. Testing of the ship template has started and is going well. Risks: supplier lead times remain a watch item. RAG: Amber."

Everything in that is true. Nothing in it is useful. The reader finishes it knowing that people were busy, and has no idea that the second tranche hardware is now arriving after the ships are scheduled to be fitted.

Here's the same week, rewritten:

"Tranche 2 hardware now lands 21 October, which is three weeks after the two ships booked into the October dock. Those two will slip to the February dock unless we re-sequence.

I need a decision from Priya by Friday: either we swap the February pair into the October dock instead, which holds the overall date, or we pay for expedited freight at roughly the cost of one ship's fit. My recommendation is re-sequence, because the kit for the February pair is already in the warehouse and the freight spend buys us nothing we can't get for free by moving.

Everything else on track: deck surveys complete on ships one and two (96 of 96 spaces), ship template in test, fit-outs resume 6 October."

Eighty words shorter. It contains a number, a date, a named person, a choice, and a recommendation. The reader can act on it in fifteen seconds. And crucially, nobody can later say they weren't told, because the bad news is the first thing on the page rather than the ninth thing in a list.

The fastest way to find out whether your update is any good is to try writing it as a message you'd send to your sponsor on their phone. Two sentences, no formatting, no headings to hide behind. If you can't get it into two sentences, you haven't worked out what the week meant yet, and sending 900 words is not going to fix that. It's just going to move the problem to someone with less context than you.

Do that first, then let the longer version grow underneath it for whoever wants the detail. The order matters. Almost everyone writes the long one and then tries to summarise it, and the summary always ends up being a summary of the document rather than a summary of the situation.

Write your next update in this order. First sentence: where you are against the date, with a number in it. Second sentence: the one decision you need, who owns it, and by when. Then stop, read those two lines, and delete every line below them that the reader cannot act on or would not notice missing.

If deleting the rest makes you nervous because it's the evidence of the work, send the two lines anyway and keep the detail in a linked document. The people who want it will click. Almost nobody will, and that's the finding.