You post a clear update in your team channel. Everyone who reads it understands it, because they were all there for the last three weeks. Two days later your manager copies your paragraph into an email to somebody two levels up, and now your words are in a room you are not in, being read by a person who does not know what the Tuesday job is or who Marcus is.
Almost everything you write that matters gets relayed at some point. The message is not finished when your team understands it. It is finished when it survives being pasted somewhere else with no thread above it.
That gives you a simple test to apply before you hit send. If a stranger read only this paragraph, would they know what happened, what it affects, and what is being asked for?
A few things make the difference. Name things in full the first time. The nightly customer import, not the Tuesday job. Say what it means in the reader's terms rather than the system's. Customers cannot download their invoices is a sentence anybody can act on. The exporter is throwing is not, unless you already know what the exporter is for.
Keep the whole point inside one paragraph, because one paragraph is the unit that gets forwarded. The context two messages up will not travel with it. Avoid pronouns that reach backwards into the thread, since this and that lose their referents the moment the message moves.
Put the date and the ask together. A relayed update without a date invites somebody to act on a situation that resolved itself last week.
And never let a decision live only in a screenshot or a reply chain, because neither can be searched or quoted by the person trying to help you.
There is a second reason to do all this, which is that you are making it easy for somebody to advocate for you. Your manager forwarding a clean paragraph is your work arriving upstairs in your own words instead of their summary of it.
Monday: take the last update you wrote and rewrite it as if the reader joined the company this morning.
– Asael Shinder
