I communicate asynchronously by writing so another person can understand the context, decision, and next step without scheduling a meeting. The goal is not fewer conversations at any cost; it is fewer unnecessary interruptions.
I include the information needed to act
My update answers: What happened? Why does it matter? What decision or action is needed? Who owns it? By when? I link the source document rather than scattering versions across messages.
I distinguish updates from decisions
An update may require no response. A decision request needs options, recommendation, tradeoffs, and a deadline. I label the difference so people know how to engage.
I write for people in other time zones
I avoid “today” when the date could be unclear and use exact dates and time zones. I do not create artificial urgency because I sent a message near the end of my own day.
I document the result
After discussion, I place the final decision in the shared source with owner and date. A long chat thread should not become the only record.
I know when to switch to live conversation
Complex conflict, sensitive feedback, rapidly changing incidents, and ambiguous high-stakes decisions may need a call. I use the call to resolve the issue and written notes to preserve the outcome.
A format I use
- Context: one or two sentences
- Current status: verified facts
- Decision needed: specific question
- Recommendation: my proposed option and why
- Owner/date: who responds and by when
Good asynchronous communication reduces dependence on memory and availability. It makes work easier to continue, review, and hand over.