Writing Is the Interface of a Distributed Team
In an office, clarity can be recovered in a hallway. Across time zones, the document is the team. It is worth learning to write one well.
A colleague once described our first year of distributed work as a series of meetings held to explain documents that should have explained themselves. She was right. We were writing as though someone would be standing beside us to fill in the gaps.
The document is the meeting
When work spans time zones, a well-written page does something a meeting cannot: it serves everyone at the moment they are ready, in their own order, at their own pace, and it is still there in six months when a new person asks why.
That only holds if the page is genuinely self-contained. Ours were not. They assumed context, referenced conversations, and buried the decision under the background.
Decision first, reasoning after
We now write every proposal in the same shape.
- What we are going to do, in one sentence.
- What this is instead of, and why.
- What we are not doing, deliberately.
- What would make us change our minds.
The order matters. A reader who agrees can stop after the first line. A reader who does not knows exactly where the disagreement lives, and can argue with the reasoning rather than guessing at it.
If your reader has to reach the last paragraph to learn what you want, you have written a mystery, not a proposal.
Write for the person who joins next year
The most valuable documents in our archive are the ones that record why an obvious-looking option was rejected. Those save more time than any amount of onboarding material, because they answer the question every new person eventually asks.
It costs one extra paragraph at the time and repays it for years.
Shorter is kinder, but clear beats short
There is a fashion for brevity that quietly shifts the effort onto the reader. A three-line message that produces four clarifying questions is not efficient. We aim for the shortest version that does not need a follow-up, which is usually a little longer than the shortest version.
The habit that made the difference
Before publishing anything longer than a page, read it once as if you had never seen the project. Every time we do this, something obvious gets cut and something assumed gets stated. It takes five minutes and it is the difference between a document people use and a document people ask about.
