When a written update beats a meeting
Half of recurring meetings are a document being read aloud slowly. The other half would be ruined by a document.
Replacing meetings with writing is good advice applied indiscriminately, which is how teams end up with silent weeks and unresolved disagreements. The useful version is knowing which half is which.
What converts cleanly
Anything where information flows one way. Status, progress, numbers, what shipped, what is planned: nobody needs to be in a room for that, and reading it takes a quarter of the time that hearing it does.
The tell is whether the meeting would still work if half the people said nothing. If it would — and in most status meetings it already does — you are holding a meeting to make a document feel official.
What must not be converted
Disagreement, ambiguity and anything with feeling in it. In writing, a disagreement between two people becomes a sequence of increasingly careful paragraphs, each one read in the worst available tone, and it takes four days to reach what a fifteen-minute call resolves.
Same for a decision nobody can articulate yet. Writing forces clarity, which sounds like a virtue until you need the vague middle stage where people think out loud. If you cannot yet state the question in one sentence, meet.
A written update needs a deadline and a place to reply
A document sent with no expectation is a broadcast into nothing. Half the recipients skim it, nobody responds, and two weeks later people are acting on different assumptions — which is worse than the meeting you removed.
Say when you need a response and what kind: "comments by Thursday, silence means agreed" is a working contract. Without that sentence, silence means nothing, and you will discover which at the worst possible moment.
Put the decision at the top
People write updates as narrative — what happened, then what it means, then what is needed — because that is the order things occurred. Readers do not read in that order; they read the first two lines and skim the rest.
Open with what you need from them, then the context underneath. It feels abrupt to write and is the difference between an update that produces answers and one that produces a follow-up meeting about the update.
Questions people actually ask
Which meetings can become documents?
Anything where information flows one way — status, progress, numbers, what shipped. The tell is whether the meeting would still work if half the people said nothing; in most status meetings it already does.
Which meetings should stay meetings?
Disagreement, ambiguity, and anything with feeling in it. In writing a disagreement takes four days and is read in the worst available tone. If you cannot state the question in one sentence yet, meet.
How do I make people read a written update?
Give it a deadline and a reply channel — “comments by Thursday, silence means agreed” — and put what you need from the reader in the first two lines, with the context underneath.
