When a team works in different places and time zones, writing becomes the main way work gets done. A vague message that would be clarified in seconds at a shared desk can cost a day when the reader is asleep while you are working. Good remote writing is not about writing more; it is about writing so the reader can act without having to ask a follow-up question.
Write messages that stand alone
Avoid messages like "Hi, got a minute?" that force the reader to wait for the real question. Put the context and the request in the same message:
- what you need;
- why you need it;
- by when;
- any links or files the reader needs to answer.
If the message is long, start with a one-line summary so the reader knows immediately what is being asked.
Make requests easy to answer
Numbered questions get numbered answers. Offer options when possible ("Should we ship Monday with the known issue, or Wednesday with the fix?") rather than open questions. State your own recommendation, which often turns a discussion into a quick approval.
Use the right channel
Chat is good for quick, low-stakes coordination. Decisions, plans and anything people will need to find later belong in a document or ticket that can be searched and linked. A useful habit is to summarize a long chat discussion in a short document and post the link back in the chat.
Write asynchronous status updates
A regular written update can replace many meetings. A simple format works well:
- Done: what was completed since the last update.
- Next: what you plan to do.
- Blocked: anything you need from others, with names.
Keep updates short and specific. "Fixed the export bug; PR is ready for review" is more useful than "Worked on bugs".
Record decisions
Remote teams lose track of why something was decided. A short decision record captures the date, the decision, the options considered, the reasoning and who was involved. Keep these records in one place so new team members can catch up without asking everyone.
Write documents people can skim
Lead with a summary, use descriptive headings and keep paragraphs short. Mark the status at the top (draft, under review, final) and the date of the last update. When asking for feedback, say what kind you need and by when, for example "comments on the approach by Thursday; wording can wait".
Be precise about time
"End of day" means different times for different people. Use specific times with a time zone, or dates in an unambiguous format. When scheduling, list the time in the main zones your team uses.
Keep a shared glossary and templates
Distributed teams often use the same word for different things, or different words for the same thing. A short glossary of project terms, kept with the team's documentation, prevents misunderstandings that are slow to untangle by message. Templates help in the same way: a standard layout for proposals, incident notes or handovers means readers know where to look for the summary, the owner and the deadline. Templates should be short and easy to adapt, or people will stop using them.
Write handovers before you are away
Before time off or a change of responsibility, write a brief handover: current work, open questions, where files live and who can make decisions in your absence. This lets colleagues continue without waiting for you.
Mind the tone
Written messages lose tone of voice, so brief messages can read as curt. A short greeting, a thank-you and clear wording go a long way. When disagreeing, focus on the work rather than the person, and consider a call for sensitive topics, followed by a written summary.
Key takeaways
- Make every message self-contained, with the request and deadline included.
- Move decisions and plans out of chat into searchable documents.
- Use a consistent, short format for status updates.
- Be explicit about times, owners and the feedback you need.