Async wins when time zones, evidence, or drafting matter more than instant chat

Asynchronous communication—email, shared docs, recorded messages—shines when people are spread across time zones, when you need a written record of decisions, or when a topic requires careful wording rather than spontaneous debate. Meetings work well for resolving ambiguity and making quick group decisions, but they force everyone to be present at the same moment, which can be inefficient if the goal is simply to share information or gather feedback on a draft. The key contrast: use async for durable, reviewed output; use a meeting for live, interactive problem-solving.

A useful trick: if you find yourself scheduling a meeting just to read out a document or update a status, switch to async instead. Another hint: when a question lists constraints like 'team members in three different countries' or 'a complex proposal needing legal review', async is almost always the better choice. Watch out for exam questions that imply async is always slower—it can actually be faster because people work at their own pace and don't waste time in transit or waiting for turns to speak.

To remember the point, think of the acronym TED: Time zones, Evidence (written record), Drafting (careful wording). If the scenario ticks any of those boxes, async beats a meeting. For a quick self-test, ask: 'Would a written message still be useful tomorrow?' If yes, go async.