Async vs Sync: When a Meeting Is Worth It (and When It's a Message)

You don't need another meeting. You need a faster way to decide whether the thing in front of you is actually a meeting. Most of what lands on a calendar is a status update, a question, or a decision that one good paragraph could have settled. The skill isn't running better meetings. It's knowing, before you send the invite, whether a message, a doc, or a 3-minute video would do the job better and cost the team less.

What async and sync actually trade

Synchronous communication means everyone is present at the same time: a call, a stand-up, a screen-share. It's expensive because it multiplies. A 30-minute meeting with six people isn't 30 minutes, it's three hours of paid attention, plus the context-switch tax on either side. Its payoff is bandwidth and speed: you can resolve ambiguity, read tone, and reach a hard decision in one pass.

Asynchronous communication means people respond on their own schedule: a Slack thread, a shared doc with comments, a Loom walkthrough, a written spec. It's cheaper and it scales, it creates a searchable record, and it protects deep work. Its weakness is latency and the failure mode where a 12-message thread is really a 5-minute conversation that nobody had the nerve to schedule.

That number is the whole problem in one line. More than half of meetings aren't planned, they're reflexes. Someone has a question and reaches for a call because typing it out feels like work. The same Microsoft research found employees get interrupted roughly every two minutes during core hours by a meeting, email, or ping. When interruption is the default, focus becomes the thing you have to schedule.

The decision checklist: should this be a meeting?

Run the request through these questions in order. The first "yes" usually tells you the format.

1. Is it a real decision with trade-offs and disagreement? Meet. Branching debate where people need to react to each other in real time is what sync is for.
2. Is it sensitive, emotional, or about a person? Meet, or at least call. Feedback, conflict, bad news, and anything where tone matters do not belong in a thread.
3. Is it brand-new, ambiguous, or undefined? Lean sync. The first conversation on a fuzzy problem is faster out loud. Once it has shape, move it to a doc.
4. Is it a status update, an FYI, or a number everyone already has? Async. This is the single biggest meeting to kill. Post it; let people read it in 90 seconds.
5. Is it a yes/no or a quick question? Async. Send the message. If three round-trips don't resolve it, then call.
6. Does it need a walkthrough of something visual? Record a video. A 3-minute Loom of your screen beats a 30-minute call to demo the same thing, and ten people can watch it whenever.
7. Does it span time zones or include people who'd otherwise just listen? Default async. Don't make someone join at 9pm to hear an update they could read.

Make async actually work (most teams do it badly)

Async fails when it's just sync with delays. A good async message is self-contained: the context, the specific question, the options you see, your recommendation, and a deadline for a reply. "Thoughts?" is not async communication, it's a meeting you've postponed. The goal is that the reader can act without a single follow-up.

And when you do meet, protect it. Require an agenda or it gets declined. Invite the people who decide, not the people who might be curious. Default to 25 minutes instead of 30, end with written owners and next steps, and post that summary so nobody who skipped the meeting has to ask what happened.

A simple default to adopt this week

Set the team's baseline to async, and make sync the thing you justify. New ad-hoc call? Try a message first. Recurring status meeting? Replace it with a written update for a month and see what breaks. Demo? Record it. You'll claw back hours of focus time, and the meetings that survive will be the ones genuinely worth everyone's presence.

The meetings still worth having tend to share a shape: a decision is on the line, people disagree, and the conversation needs to branch. Everything else is a document, a message, or a video waiting to be written.