Async communication_

Asynchronous communication (async comms) is referring to the idea that you're able to communicate with others while they may be currently unavailable.

Examples of this are email, Slack, and even adding a comment in Jira tagging them, etc. If the message can be queued and consumed later, it's async.

This is in contrast to "synchronous comms" that block all present parties from other potential tasks and discussions, a la phone calls, meetings, coffee runs.

Both have advantages and disadvantages, most notably async allows higher rates of consumption, time management, and multiple tasks running at once (hence async), while synchronous allows for more bandwidth to the current topic, giving more immediate clarity and less follow up.

Project kickoffs, and board meetings especially for example are usually done synchronously, as it allows all participants to ask questions and get immediate answers. However, follow-up questions and discussions are usually done async.

Asking co-wokers clarifying questions is usually done async, as it allows them to answer when they're free, and you to continue working on other tasks. Other async messages, such as team emails, Jira mentions, and Slack DMs, will 'queue up' for them to answer when they're ready.

Larger or more "traditional" companies tend to use synchronous comms, while startups and small businesses target async, though the opposite is also entirely possible with small companies wasting too much time in meetings, and larger companies doing everything they can to avoid them. You make your own reasons as to why.

Generally I'd recommend as much async as possible.

Have a play with the interactive below, it's a "fun" little "game" that lets you swap between synchronous and async comms and see how it affects the team's productivity.