Write for the Next Reader

Imagine finishing your afternoon in Singapore while a colleague in London is opening their laptop. A message saying “Can you check this?” transfers uncertainty rather than work. Which version? What kind of check? Is the request urgent, and who decides what happens afterward? Each missing detail can consume another working cycle.

Asynchronous communication is not simply communication without a meeting. It is communication designed for readers who cannot immediately ask a follow-up question. Good writing reduces that dependency while leaving room for disagreement, clarification and human conversation.

Lead with the reader’s job

Put the requested action near the beginning. Label a message as a decision request, a review, a question or an update. Those categories imply different kinds of attention. An update should not secretly require approval; a decision request should not be buried beneath a long account of the week.

Then provide the minimum context needed to act responsibly. Explain what changed, why it matters and where the source material lives. Link to the current document rather than attaching another unlabelled copy. If a link needs special access, check permissions before sending the request.

Separate context from the decision

A reader should not have to infer which sentence changes the plan. Use a short summary followed by evidence, options, trade-offs and the proposed next step. For a complicated choice, a decision record can include the alternatives rejected and the conditions that would justify revisiting the decision.

This practice resembles the architectural decision record, or ADR, used in software teams, but the habit works beyond software. A hiring process, service workflow or editorial policy can also benefit from a dated explanation of what was decided and why. Keep the record proportionate to the consequence.

Write enough to make the next action safe, not enough to prove how much work you did.

Make timing explicit without manufacturing urgency

“Today” has different meanings in Tokyo, Nairobi and Vancouver. For a real deadline, give a full date and a time zone. UTC can be useful for shared records, while calendar invitations should display local time for each participant. Check daylight saving changes instead of assuming the offset stays fixed.

For ordinary requests, a working-period response expectation is often kinder than an elapsed-hour target. A colleague should not lose their whole response window while asleep. Agree what happens during leave, public holidays and reduced schedules, and identify a backup for genuinely time-sensitive work.

Keep one durable home for the answer

Chat is useful for discovery, coordination and quick clarification. It is a poor sole archive for a decision that future colleagues need to find. After a discussion, move the outcome into the agreed project record and link back to it from the conversation.

Use descriptive headings and a consistent status such as proposed, accepted or superseded. Mark old guidance clearly rather than letting competing versions accumulate. Search becomes more useful when the title names the actual work instead of an inside joke or an unexplained acronym.

Write for different readers, not an imagined average

International teams bring different language backgrounds and communication conventions. Prefer direct sentences, define unfamiliar abbreviations, and avoid treating idioms as shared knowledge. Plain English is not simplistic; it gives more colleagues access to the same decision.

Make important information available as text even when you share an audio or video explanation. Add captions or a transcript where appropriate. W3C’s Web Content Accessibility Guidelines, commonly called WCAG, offer a useful accessibility reference, though a readable update alone does not establish compliance.

Know when to change channels

If a thread repeats the same misunderstanding, stop adding increasingly defensive paragraphs. Summarize the unresolved question, offer a focused conversation, and let participants know what preparation would help. Afterward, return the outcome to the written record so attendance does not become a prerequisite for understanding.

• The opening names the action or makes clear that no action is needed.
• The reader can find the current source and has permission to use it.
• The response window respects local working hours.
• The owner and next step are explicit.
• The decision will remain findable after the chat moves on.

Try these checks on one recurring update. Ask the next reader which question they still had to ask. That answer is more useful than a rigid word-count target or another mandatory reporting template.