The standup is gone and nobody told you what replaces it. That is the actual situation. Somebody decided the fifteen minutes were not earning their keep, the invite disappeared, and the expectation that you all know what each other is doing stayed exactly where it was.
So you write something. And the thing you write is either a list of what you did, which nobody needs, or a paragraph of reassurance, which nobody believes.
Here is the update that does the standup’s job. It is one artifact, and most of this post is spent on why each line is worded the way it is — because the wording is the whole of it. The structure is trivial. Anyone can produce the structure. The wording is what decides whether a reader acts.
What the standup was actually doing
Three things, and only three.
It surfaced a blocker before it cost a second day. Someone said “I’m stuck on the staging credentials” out loud, and someone else said “I have those.” The value was not the reporting. It was the collision.
It kept a shared picture roughly current. Not accurate — roughly current. Enough that when a decision came up, people knew which parts of the system were in motion.
It gave the work a deadline shaped like an audience. You did not want to say “same as yesterday” three days running. That is a weak forcing function and a slightly humiliating one, but it was doing work.
A written status update can do the first two well and the third badly. Know that going in. Nothing you write will make someone uncomfortable the way a room does. If your team’s only functioning accountability mechanism was social discomfort in a video call, writing will not replace it, and you should stop reading and go argue for the standup instead.
The update, filled in
This is a real-shaped week: a migration that is about ten days behind, one genuine blocker, one decision waiting on someone who has not replied, and a piece of good news that is smaller than it sounds.
Payments migration — week of 14 April
Owner: you · Next update: Monday 21 April
Where it is: behind. We planned to have the write path live on
staging by today. It is not. Realistic date is 28 April, which is
ten days later than the plan and eight days before the vendor
contract lapses. That is still inside the window but there is no
slack left in it.
What I need from someone:
- Marta: the finance sign-off on the reconciliation report format.
It has been open since 2 April. If it is not signed by Thursday
I will ship the current format and we change it later, which
costs about two days in May. Reply with "go" or "wait".
- Anyone with prod DB access: we need one 20-minute window on
Wednesday or Thursday morning to run the row-count check
against live. Claim one and put it in the channel.
Why it slipped: the legacy table has two columns that hold the
same value and disagree about 4% of the time. We did not know
that when we estimated. Resolving each disagreement needs a rule
from finance, we have rules for two of the five cases, and the
remaining three are the ten days.
What is done: read path is live on staging and has been serving
internal traffic since 8 April with no errors. Reconciliation
script is written and tested against the sample export.
What I am not doing: the archive backfill. It was in the original
scope. It is not needed before the contract date and I have moved
it to a follow-up. Say something this week if you disagree.
Risk I am watching: if the three remaining disagreement cases each
need a separate finance decision rather than one rule, add another
week. I will know by Wednesday.
Four hundred words at most. It took twenty minutes to write, and about six of those were spent on the third paragraph.
Why it is worded that way
“Where it is: behind.” The first word after the label is the answer. Not context, not a recap, not “as you know”. A reader who stops after eleven words has the thing they needed. Every other ordering — background first, conclusion last — is a bet that the reader will finish, and you will lose that bet with the people whose attention matters most.
A date, not an adjective. “Slightly behind” is unfalsifiable and everyone reads it as differently sized. “28 April, which is ten days later than the plan” can be argued with. You want it argued with. An update nobody can disagree with has told them nothing.
The comparison to the constraint, in the same sentence. Ten days late means nothing on its own. Ten days late against a contract that lapses eight days after the new date means something, and it means it without a follow-up question. Whoever reads this now knows how worried to be, which is the actual thing they are trying to work out.
“What I need from someone” comes second, not last. This is the part most people put at the bottom, after the detail, as a kind of polite conclusion. Move it up. If the update is doing anything at all it is extracting two specific actions from two specific people, and those people will not read to the end.
The ask is addressed by name and bounded by a consequence. Not “would be great to get sign-off on the report format”. A named person, a date, and what happens if the date passes: I will ship the current format and we change it later, which costs about two days in May. That sentence is doing three jobs. It tells Marta the cost of her silence. It tells her the project is not blocked on her, which paradoxically makes a reply more likely, because a person who thinks they are holding up a whole team sometimes goes quiet out of dread. And it pre-authorises your own decision, so that if Thursday passes you act without a second round of asking.
“Reply with ‘go’ or ‘wait’.” The reply has been made cheap. A request that requires the reader to compose something is a request that competes with their inbox. A request that can be answered with one word gets answered on a phone in a lift.
The second ask has no name on it and that is deliberate. Nobody owns prod DB access; four people have it. Naming one of them makes it their job and they may be away. Naming none of them makes it nobody’s job. “Claim one and put it in the channel” is the middle: a specific action, a public claim, and a visible gap if nobody takes it.
“Why it slipped” is one cause, stated plainly, with a number in it. Two columns hold the same value and disagree 4% of the time. That is a fact about the system, not a fact about the team’s diligence, and it is checkable. Compare “we hit unexpected complexity in the data model”, which is the same sentence with the information removed. The removal is not an accident; vague slippage language exists to prevent exactly the conversation you should be inviting.
“What is done” is third, not first. It is the part you most want to write and the part they least need. Two lines. Both of them are evidence rather than effort: the read path has been serving internal traffic since 8 April with no errors is a claim someone could falsify. “Made good progress on the read path” is not.
“What I am not doing” is the section that separates this from a report. You have cut scope. Say so, in the update, with a one-line reason and an explicit window to object. Scope cut silently is scope cut that resurfaces in October as “I thought the backfill was part of this”. The sentence say something this week if you disagree converts your unilateral decision into a decision the group had a chance to reverse, which is what you will need when it is questioned later.
The risk is one risk, with a date attached to when the uncertainty resolves. A risk register with six items in a weekly update is a way of being unfalsifiable at scale. One risk, the one that would actually change the plan, and I will know by Wednesday — so the reader knows the next update is worth opening.
The week when nothing happened
Most weeks are not that week. Most weeks are grinding, and the temptation is either to skip the update or to pad it into looking like a week.
Do neither. Send this:
Payments migration — week of 21 April
Owner: you · Next update: Monday 28 April
No change to the date. Still 28 April.
Three of the five reconciliation rules are now agreed. Two left.
Both are with finance and neither is contentious; I expect them
this week.
Nothing needed from anyone.
Sixty words. Sending it is the point.
An update whose only content is “no change” does two things a skipped week does not. It confirms the date is still the date, which is the single question every reader has. And it keeps the artifact in the reader’s peripheral vision, so that when a week does need something from them, the message arrives in a slot they already check rather than as an alarming novelty.
The “nothing needed from anyone” line matters more than it looks. Without it, the reader has to scan for an ask. With it, they are done. You are spending a sentence to save forty people ten seconds and, more usefully, to make the weeks that do carry an ask visibly different.
The version that failed
Here is what the first update on this project actually looked like, before any of the above.
Payments migration update
Hi all — quick update on where we are with the payments
migration. It's been a busy couple of weeks and the team has
been making solid progress across a number of workstreams.
The read path work is largely complete and we've been doing
extensive testing. We've hit some unexpected complexity in the
data model which has had a knock-on effect on the timeline, but
we're working through it and I'm confident we'll get there.
We're also making progress on reconciliation. There are a few
open questions with finance that we're chasing.
Happy to answer any questions — let me know if you'd like to
grab time to go through it in more detail.
Thanks all!
Nobody replied to it. Three specific reasons, and only the third is about writing.
There is no date in it. Not one. “A knock-on effect on the timeline” is the only reference to schedule, and it is unquantified, which means every reader supplies their own number. The optimist supplied three days. The person who would have escalated supplied three days. Six weeks later the actual number arrived at once, and by then the honest early warning had become a surprise, which is a different and much more expensive category of news.
The ask is invisible. “A few open questions with finance that we’re chasing” contains a real blocker — the sign-off that had been open since 2 April — but no name, no date, and no consequence. It is written as a status of the ask rather than as the ask. Finance did not know they were on the critical path, because this sentence does not tell them.
The last line invites the meeting. Let me know if you’d like to grab time to go through it in more detail. That is a written update whose closing move is to offer a call. It signals that the document is not the real account, that the real account is verbal and available on request, and that the reader who wants to know what is going on should book. Somebody did. The standup came back in a different shape and with more people in it.
The fourth thing, which is not a writing problem at all: this went to a channel that thirty people mute. That failure has its own post, because the fix is not editorial.
Where it goes, and when
One place, and it is the same place every week. A channel people actually read, a mailing list, a document with a stable URL that you bump. Not a document that lives in a folder and gets linked when someone asks. If a reader has to remember where the update lives, the update does not exist.
Post the body, not a link to the body. A link asks for a click, a click asks for a load, and a load asks for a decision about whether this is worth the next ninety seconds. Paste the text. If it is too long to paste, it is too long. Link the detail from inside it.
Same day, same time, before the day fills up. Monday morning beats Friday afternoon for a reason that has nothing to do with when you finish the work: an update read on Monday can still change the week. A Friday update is read Monday anyway, badly, in a scroll of everything that arrived over the weekend.
Announce the next one inside this one. Next update: Monday 28 April. It costs four words and it converts the update from a thing you send when there is news into a thing with a schedule. Missing a scheduled artifact is visible. Missing an unscheduled one is not.
What this costs
Be honest about it, because posts that pretend writing is free are the reason people stop.
It is slower than a call. The reconciliation disagreement, resolved in the update, took two rounds and four days. In a standup it would have taken ninety seconds. That trade is worth it when the audience is forty people and worth it less when the audience is three.
It is a record. Realistic date is 28 April is searchable, forwardable, and permanent. It will be quoted back to you in a review. That cuts both ways — it is also the reason you have proof you flagged the slip early — but the asymmetry is real: the sentence that protects you is the same sentence that convicts you, and you do not get to write one without the other.
Somebody will read the honesty as pessimism. Writing “behind” in the first line, in a durable artifact, in front of people who do not know the detail, feels expensive. It is expensive, once. It is much less expensive than the version where nobody knew until May.
It does not create attention. Writing well gets you read by people who were going to read something. It does nothing about the reader who was never going to open it, and the assumption that quality solves distribution is the most common mistake made by people who write good updates. That is a distribution problem, and it has its own diagnosis.
When the honest answer is a meeting
Three cases. In all of them, stop drafting.
The disagreement is about values rather than facts. Two people want different things and both know all the same information. A document does not converge that. It gives each of them a durable artifact to be right at, and the next version is longer.
The news is bad enough that the delivery matters. Cancelling a project, missing a date that someone has personally staked their reputation on, telling a team their work is being shelved. Write the artifact — you will need it — but do not let it be the first anyone hears. Say it, then send it.
You do not yet know what you think. An update is a report on a position. If you are still forming the position, a conversation is faster and the document you write afterwards will be better. Half the bad updates in the world are people thinking out loud in public and calling it transparency.
Everything else is a document.
The rest of this cluster
Start here
Take your last update. Find the first date in it. If there isn’t one, that is the edit. If there is one, check whether it is compared to anything — a plan, a deadline, a constraint — because a date with nothing to measure it against is just a number you have made yourself accountable for.
Then find the ask, and check that it has a name on it, a day, and a consequence for silence. If you can only make one change this week, make that one. Rewriting the rest for a reader who skims comes after.