Async by Default: Rethinking the Meeting
The default should be a message, not a meeting. Here's what changes when a team actually commits to that.
Most teams treat meetings as the default way to communicate and async messages as the fallback for when a meeting can't be scheduled. Async-first teams flip that: the default is a written message, a recorded update, or a shared document, and a live meeting is the fallback for the rare cases that genuinely need real-time back-and-forth.
The difference sounds small. In practice it changes almost everything about how a day feels.
The real cost of a meeting isn't the meeting
A thirty-minute meeting with six people isn't thirty minutes of cost — it's three hours of combined attention, plus the fragmentation cost of breaking six people's days into pieces around it. A message that takes five minutes to write and two minutes to read, six times, costs a fraction of that, and it doesn't require everyone to be available at the same moment, in the same time zone, at the same time.
Most of what fills a calendar doesn't actually require synchrony. A status update doesn't need a meeting. A decision that only needs one person's input doesn't need six people in a room. What does need a live meeting is genuinely rare: a disagreement that needs real back-and-forth to resolve, a brainstorm that benefits from momentum, a relationship that needs the warmth only a live conversation carries. Everything else is a message wearing a meeting's clothes.
What async-first actually requires
It's not just "send more Slack messages." A team that's genuinely async-first tends to do a few specific things differently:
- Write updates that don't require a reply. A good async update answers questions before they're asked, so the reader doesn't have to schedule time to interrogate it.
- Default to a longer response window. If everyone is expected to reply within ten minutes, you haven't actually gone async — you've just moved the meeting into a chat window and kept the same expectation of immediate availability.
- Protect focus time explicitly. Async only reduces interruptions if people also agree not to treat a written message like a phone ringing. Otherwise you've traded one interruption format for another.
What it gives back
Teams that make this shift consistently report the same result: not less communication, but communication concentrated into blocks instead of scattered across the whole day. Focus time stops being the leftover minutes between meetings and becomes the default state, with meetings as the occasional exception.
This is also, not coincidentally, what makes shared focus spaces work at all. A room full of people quietly working only stays quiet if the team culture around it doesn't expect an instant reply the moment someone's away from their inbox. Async-first isn't really a communication policy. It's what has to be true for deep, uninterrupted work to be possible on a team of more than one person.
