Your Async Update Is All They Read

In a distributed team, your written update is not a summary of the work — for most of the people who matter, it is the work. Colleagues three time zones away will never see you think, hesitate, or recover. They will see a paragraph in a channel, skimmed between meetings, and from that fragment they will infer your judgement, your pace, and whether the project deserves their attention.

The instinct, once you notice this, is to write more. Resist it. An update that runs to six paragraphs will be read as far as the second, and the reader will leave with whatever impression the second paragraph happened to create. Length is not thoroughness; it is a tax you levy on everyone downstream. The discipline worth building is compression — saying the consequential thing first, and letting the rest earn its place.

Start with the sentence you would say if the reader closed the tab immediately afterwards. Most people bury it: they narrate the week chronologically and arrive at the point in the final line, by which time nobody is still there. Invert the order. State the status, the decision you need, or the number that moved — then supply the reasoning. Journalists have called this the inverted pyramid for a century; it has never been more useful.

Asynchronous writing removes the repair channel. In a room, a raised eyebrow lets you rephrase before a misunderstanding hardens; in a thread, your ambiguity travels for eight hours before anyone can query it. So hedge less. "We might slip" forces the reader to guess how much and by when; "We will miss Thursday by two days unless legal can sign off tomorrow" costs the same breath and settles the question outright.

There is a countervailing risk, and it is worth naming. Precision invites accountability, and the writer who commits to a date in public can be held to it. That is precisely the point. Vagueness feels safe because it defers the reckoning, but it also drains your words of value; a colleague who cannot act on what you wrote will eventually stop reading it. Credibility compounds, and so does its absence.

Write for the reader who has forgotten everything. You have been immersed in this problem all week; they last thought about it a fortnight ago, in a different meeting, about a different version. One clause of context — "the migration we paused in June" — spares them a search through the archive. Format for the eye, too: short paragraphs, one idea each, and bold only where you genuinely need someone to stop.

Then close the loop. Every update should end with what you want to happen next — a decision, a review, a silence you will interpret as consent. "If I hear nothing by Friday, I'll proceed with option B" converts a broadcast into a mechanism. It also gives anyone who disagrees a clear moment to push back, which is far cheaper than discovering their objection after the work is done.

None of this is about writing well in a literary sense. It is about accepting an unglamorous fact of distributed work: the version of you that exists in other people's heads is assembled almost entirely from text they skimmed. Give that version a fair chance. Lead with the point, quantify the risk, name the ask — and your update stops being an obligation you discharge and becomes the instrument through which you actually lead.