Async Teamwork: Write Updates That Move Work Forward

Asynchronous work depends on written context. A useful update lets a teammate understand the situation and respond without a chain of clarifying messages. It does not need to be long; it needs to answer the reader's likely questions.

Use a simple structure

Start with the project or decision. State what changed since the last update, what is on track, and what is blocked. If you need input, ask a specific question and say who should respond and by when. End with the next checkpoint so everyone knows when to expect another update.

Link to the working source

Keep detailed notes in the shared document or tracker and point to the relevant section. Avoid pasting a new copy of information into every conversation. This keeps the working source easier to maintain and reduces the risk that two versions drift apart.

Choose the right level of detail

Use a short message for routine progress and a fuller note for a decision with tradeoffs. Make urgency explicit rather than relying on an unread message. For sensitive topics or difficult feedback, choose a private conversation instead of a broad channel.

Written updates do not replace conversation; they make the conversation more focused. When your team uses a consistent format across Mail and its shared Docs or Sheets, teammates can catch up on their own time and spend live meetings on the work that needs discussion.