async home / Playbook
Team workflows / practical steps
Write updates that move work forward
Replace unclear status messages with a written decision, a named owner and a useful next step.
STEP 01
Choose the right communication mode
Use a written update when people need context but do not need to respond simultaneously. Use a call or urgent escalation for incidents, sensitive conflict or a blocker that cannot wait. Record the outcome afterwards so absent teammates can follow the decision.
STEP 02
Make the update self-contained
Begin with the outcome or question. Add the relevant background, what changed, evidence and any options considered. Link to one maintained source of truth instead of scattering different versions across chat, email and documents.
STEP 03
Name the next action
State who should act, what response is needed and when it would be useful. Include the time zone for deadlines. Distinguish an informational update from a request for approval so readers know whether they are blocking progress.
STEP 04
Close the loop visibly
Record the decision, its owner and the next review point in the original work item. If a discussion moves to a call, bring the result back. Archive superseded guidance or label it clearly to prevent an old answer becoming the default.
Choose the right next step
- Routine progress: write a concise update with evidence and next steps.
- Ambiguous decision: state the options and ask a named decision-maker.
- Urgent incident: use the agreed immediate channel, then document the outcome.
Worked example
Instead of “API work is almost done,” write: “The import accepts the sample file; duplicate detection is still failing. Priya will fix it by Tuesday 15:00 IST. Please confirm whether duplicate rows should be rejected or merged before then.” The reader can now act without another status meeting.