An async update should let a teammate understand what changed and whether they need to act. A long activity diary is less useful than a short status with evidence and a clear next step.
Use a consistent shape
- State the outcome completed or the question being investigated.
- Link the pull request, test result, document, or example that supports the update.
- Name the blocker, decision needed, owner, or expected follow-up when one exists.
Make timing explicit
Use dates and time zones for deadlines that cross regions. If you need a response by a certain time, explain why and identify what work is waiting.
Post updates where the team can find them later. Avoid sharing credentials, private customer data, or sensitive incident details in a channel with broader access than necessary.