Choose the format based on the job
Asynchronous communication lets people respond at different times. It can protect focused work and make participation easier across schedules and time zones. But it does not mean replacing every conversation with a document. The useful question is: what does this exchange need to accomplish? An update, a decision, a demonstration, and a sensitive discussion place different demands on the people involved.
Before choosing a format, consider three things: how quickly a response is needed, how much back-and-forth the topic requires, and whether people will need to find the information later. A routine update with a deadline next week may work well in writing. A decision blocked by several competing priorities may need a short live conversation. If the outcome matters beyond the people present, record the decision in writing afterward, whatever format you used to reach it.
Write when people need to scan, search, or respond carefully
Writing suits status updates, requests with clear questions, proposals that need review, and decisions people may need to revisit. It gives readers time to consider their responses and offers a reference that does not depend on memory. Make the first lines useful: state the purpose, the action requested, who needs to act, and by when. Put essential context in the message rather than assuming everyone has followed an earlier thread.
Imagine a team planning a change to its customer help pages. A short written proposal could describe the problem, show the proposed page structure, identify open questions, and ask reviewers to comment by a specified day. That is easier to evaluate than a vague invitation to “share thoughts.” Writing becomes less effective when replies reveal that people mean different things by the same terms or are debating assumptions rather than the proposal. At that point, a conversation may be the faster route.
Record when showing is easier than describing
A brief screen recording can be useful for walking through a design, demonstrating a software issue, or explaining a visual sequence. Viewers can pause and replay it when convenient. Keep it focused on one task, say what viewers should look for, and indicate whether you want feedback or are simply sharing an update. A recording is usually a poor substitute for a concise written request: it takes time to watch and is harder to scan for one important detail.
Give people another way to access the substance. A written summary, transcript, and captions where possible help colleagues who cannot play audio, prefer to read, or use assistive technology. Check that anything important shown on screen is also described. Before recording a call or including someone else’s work, consider workplace rules and ask for appropriate permission. Recordings are most useful when they make an explanation clearer, not when they shift the effort of finding the point onto the audience.
Talk live when interaction changes the outcome
Live discussion earns its place when participants must resolve ambiguity together, weigh trade-offs quickly, or handle a topic that calls for care and immediate questions. A conversation may also help when a written exchange has grown long without producing a decision. The goal is not to gather everyone who might be interested; it is to bring together the people needed to make progress.
For example, suppose two teams disagree about which feature should ship first because each sees a different risk. A short meeting with the decision-maker and relevant contributors can surface those assumptions. Send the choices and constraints in advance so participants can prepare. During the conversation, clarify who decides, what remains uncertain, and what happens next. Then share a brief written outcome with anyone affected who could not attend.
Make response expectations visible
A format only works if people know how to use it. Set reasonable expectations for response times, distinguish urgent requests from routine ones, and avoid treating every notification as an emergency. If a message genuinely needs an immediate answer, say why and use the agreed urgent channel. Otherwise, a clear deadline gives colleagues room to plan their attention. Acknowledging a request is different from finishing the work, so make clear which response you need.
Teams can also agree where lasting information belongs. A chat thread may start an idea, but a shared note is often a better home for the final decision, its owner, and the next step. Periodically check whether the mix of messages, recordings, and meetings works for the people doing the work, including those who need accessible alternatives or have limited overlap in working hours. Good asynchronous practice is not a rule against meetings; it is a habit of choosing the least disruptive format that still helps people understand, contribute, and act.
