Why I prefer async work over meetings

I haven't had a regular meeting schedule in over two years. No daily standups, no weekly syncs, no "quick catch-up" calls that somehow last forty-five minutes.

This isn't because I'm antisocial. It's because I've found that almost every meeting I used to attend could be replaced with something better. A written update, a short video, a well-structured document. The work gets done faster, the communication is clearer, and I get my most productive hours back.

The hidden cost of meetings

Every meeting has a cost that goes way beyond the time on the calendar.

There's the context switch before the meeting, where you stop whatever you were doing and mentally prepare. There's the meeting itself, which almost never starts or ends on time. There's the recovery period after, where you try to remember what you were working on before you were interrupted.

A thirty-minute meeting doesn't cost thirty minutes. It costs about ninety minutes of productive time when you account for the transitions. If you have three meetings in a day, you've effectively lost the entire morning.

For someone who builds things (writes code, designs interfaces, solves problems), uninterrupted blocks of time aren't a luxury. They're a requirement. Deep work doesn't happen in the gaps between meetings. It happens when you have three or four hours of clear focus ahead of you.

What async looks like in practice

When I work with teams and clients, here's how we communicate:

Daily updates go in a shared channel. What I worked on, what I'm working on next, anything I'm blocked on. This takes five minutes to write and can be read by anyone at any time. It replaces the daily standup.

Design reviews happen through recorded Loom videos. I walk through the design, explain my thinking, and ask specific questions. People respond on their own schedule with written feedback or their own recordings. This is better than a meeting because people can pause, rewind, and think before responding.

Technical decisions get written up as short documents. The problem, the options, my recommendation, and the trade-offs. People comment asynchronously. By the time a decision needs to be made, everyone has had time to think it through properly instead of reacting in real time.

Urgent issues get a direct message or a phone call. Not everything can be async. But if everything is async by default, the synchronous moments carry real weight. A phone call from me means something is actually important, not just that it's Tuesday at 10am.

Why writing beats talking for most communication

When you write something down, you're forced to organize your thoughts. You can't ramble. You can't fill silence with filler. You have to actually know what you're trying to say.

This leads to clearer communication. I've seen technical discussions that would have been a confused hour-long meeting get resolved in a ten-minute written exchange because both people had to articulate their positions clearly.

Writing also creates a record. Three months from now, you can look back and understand why a decision was made. With meetings, that context evaporates unless someone took detailed notes (they didn't).

And writing is inclusive in ways that meetings aren't. Non-native speakers get time to compose their thoughts. Introverts don't get talked over. People in different time zones participate as equals instead of attending meetings at midnight.

When meetings actually make sense

I'm not anti-meeting. I'm anti-unnecessary-meeting. Some situations genuinely benefit from real-time conversation:

Brainstorming works better synchronously. The energy of riffing on ideas together creates combinations that don't emerge from written exchanges.

Sensitive conversations need tone and nuance that text can't provide. If someone is struggling, or if there's a disagreement that's becoming personal, get on a call.

Kickoffs and retrospectives benefit from the shared experience of being in the same (virtual) room. The beginning and end of a project are ceremonies that build team cohesion.

When you're stuck. If a written exchange is going in circles with misunderstandings, a five-minute call can resolve what twenty messages couldn't.

The key is treating meetings as a tool for specific situations, not as the default mode of collaboration.

Making the switch

If your team is meeting-heavy and you want to move toward async, don't flip the switch overnight. Start with one change.

Replace your daily standup with written updates for a week. See how it feels. You'll probably find that the information flows better and people appreciate getting fifteen minutes back every morning.

Then try making one regular meeting optional by providing the content as a written update or recorded video. Let people attend if they want the real-time discussion, or catch up async if they don't.

Over time, meetings become intentional rather than habitual. You meet when there's a reason to meet, not because it's on the calendar. The work fills the space that meetings used to occupy, and somehow everything still gets done. Usually better.