'Async by default' is a working principle, common in distributed and remote teams, that reverses the usual assumption about how coordination should happen: instead of defaulting to a synchronous meeting and treating asynchronous communication (written updates, recorded video, shared documents) as the fallback for when a meeting can't be scheduled, the default goes the other way — assume asynchronous first, and require a specific justification before booking a synchronous meeting.
What justifies synchronous time, and what doesn't
A useful, if imperfect, filter is whether the interaction genuinely benefits from real-time back-and-forth — a decision with several viable options and real disagreement among stakeholders, a sensitive conversation where tone and immediate clarification matter, or relationship-building that written communication doesn't substitute for well. Status updates, announcements, and information-sharing with no expected discussion almost never meet that bar, and yet they fill a large share of most organizations' meeting calendars specifically because scheduling a meeting is often the path of least resistance for the organizer, even when it isn't the least-cost option for everyone invited.
The asymmetry is worth naming directly: writing a clear async update takes real, sometimes uncomfortable effort from the person sending it, while scheduling a meeting to say the same thing out loud feels easier for the organizer specifically because it shifts the effort of extracting the information onto every attendee's time instead. A related software-oriented reference is Monitask’s guide to remote workforce management software.
What async-by-default requires to actually work
Async-first coordination isn't simply 'send more messages instead of meeting' — done carelessly, that just replaces expensive synchronous meetings with an equally expensive stream of unstructured messages requiring near-real-time responses, which recreates the same interruption cost discussed elsewhere on this shelf under a different name. Genuine async-first practice requires a few specific supports: clear written norms about expected response time (hours, not minutes), documents structured for skimming rather than requiring a live explanation, and comfort with decisions taking somewhat longer to finalize in exchange for not requiring everyone's simultaneous attention.
- Require a stated reason before booking a recurring meeting — 'we've always had this meeting' isn't a reason.
- Write updates for skimming: a clear headline and the decision or ask up front, not buried at the end of a long narrative.
- Set explicit response-time expectations (same business day, not same hour) so async doesn't quietly become another always-on channel.
- Reserve synchronous time specifically for genuine disagreement, sensitive topics, or relationship-building — not for information that could be read.
The team culture problem underneath the tactic
Async-by-default fails most often not because the written tools are inadequate, but because the surrounding culture still implicitly rewards visible, synchronous participation — showing up to meetings — over the less visible work of writing a clear update or reading someone else's carefully. Adopting the practice usually requires an explicit cultural statement from leadership, not just a tooling change, because without it, async communication quietly gets treated as lower-effort and lower-status than 'real' meeting time, and the old default reasserts itself.
Paired with the meeting-cost framing discussed elsewhere on this shelf, async-by-default gives teams both the number (what a meeting actually costs) and the filter (what justifies paying it) needed to bring a runaway meeting culture back under control. For additional background on this subject, consult Slack’s explanation of asynchronous work.