You know the feeling: thirty minutes blocked off, six people pulled away from their work, and at the end you realize the whole thing could have been a two-line message. Meetings have a way of becoming the default — the reflex for any question, decision, or update — even when they're the worst tool for the job. Knowing when something genuinely needs a meeting versus when it should have been a message is one of the highest-leverage skills a team can have, because the wrong choice quietly taxes everyone's focus.
Here's the real cost of a meeting, and how to know which channel the moment actually calls for.
Many meetings should have been a message — and knowing the difference saves enormous time.
The decision:
Default to a message; reserve meetings for what genuinely needs to be live.
The reason meetings deserve scrutiny is that their true cost is far higher than the slot on the calendar. A 30-minute meeting with six people isn't 30 minutes — it's three person-hours, and that's before you count the cost of interruption. Every attendee had to stop what they were doing, context-switch into the meeting, and then context-switch back out and rebuild their focus afterward, which research consistently shows takes far longer than the meeting itself. A single mid-afternoon meeting can fracture a whole day of deep work for everyone in the room. The calendar shows half an hour; the actual bill is a multiple of that, paid in everyone's most valuable resource — uninterrupted attention.
This is why "let's just hop on a call" is rarely as cheap as it feels to the person proposing it. The cost is real but distributed — it lands on everyone else's focus, not the organizer's — so it's easy to call meetings carelessly. A message, by contrast, lets each person engage on their own schedule, in the gaps between their focused work, without shattering anyone's concentration. When the goal can be achieved asynchronously, a message is dramatically cheaper than a meeting even though both might take "the same time," because the message doesn't impose the interruption tax on everyone at once.
The skill is matching the channel to what the moment actually requires. Meetings are genuinely the right tool sometimes — the trick is knowing when:
| Should be a message (async) | Should be a meeting (sync) |
|---|---|
| Sharing information or an update | Real-time debate or brainstorming |
| A decision that needs no discussion | Fast, iterative back-and-forth |
| Something most people can skim | Sensitive or emotional conversations |
| Anything that can wait a few hours | Building rapport or trust |
The dividing question is whether the task genuinely needs live, real-time interaction. Brainstorming where ideas build on each other in the moment, a debate that needs rapid back-and-forth, a sensitive conversation where tone and presence matter, fast iteration toward a decision — these benefit from being synchronous, and forcing them into async messages makes them slow and stilted. But sharing an update, broadcasting information, or recording a decision that's already clear needs none of that. Defaulting those to a meeting just imposes the interruption tax for no benefit. This is the same channel-selection discipline that makes async-first teams move faster: protect focus by default, and spend synchronous time only where it genuinely pays off.
The practical shift is to invert the default: assume something should be a message unless there's a clear reason it needs to be a meeting. Most teams have the default backwards — meeting first, message as the exception — which is why calendars fill with sessions that could have been a paragraph. Flipping it means every meeting has to justify itself: what about this genuinely needs live interaction? If the honest answer is "nothing, really," it should have been a message.
This isn't anti-meeting — it's pro-focus. Meetings are a powerful tool for the things that need them, and protecting them from overuse actually makes the necessary ones better, because people show up to fewer, higher-value sessions instead of being ground down by a wall of low-value ones. The teams that move fast aren't the ones that never meet; they're the ones that meet deliberately, defaulting to async for everything that doesn't need to be live and reserving synchronous time for the debates, the brainstorms, and the conversations that genuinely benefit from presence. Choose the channel on purpose, and you give everyone back the focus that careless meetings quietly steal.
To make the right call every time:
The throughline: many meetings should have been a message, and the wrong choice quietly taxes everyone's focus. A meeting's real cost is the per-attendee time plus the interruption tax of broken concentration — far more than the calendar slot suggests. Default to async, reserve synchronous time for what genuinely needs live interaction, and make every meeting justify itself. Choosing the channel deliberately is one of the highest-leverage skills a fast team can have.
Q: Why is a meeting more expensive than it looks? Because the calendar slot is only part of the cost. A 30-minute meeting with six people is three person-hours, and that's before the interruption tax: every attendee had to stop their work, context-switch in, then context-switch back out and rebuild their focus afterward — which takes far longer than the meeting itself. A single mid-afternoon meeting can fracture a whole day of deep work for everyone in the room. The cost is real but distributed onto everyone else's focus, not the organizer's, which is why "let's just hop on a call" feels cheaper than it is.
Q: When is a meeting actually the right choice? When the task genuinely needs live, real-time interaction: brainstorming where ideas build on each other in the moment, a debate that needs rapid back-and-forth, a sensitive or emotional conversation where tone and presence matter, fast iteration toward a decision, or building rapport and trust. These suffer when forced into async messages, becoming slow and stilted. The test is whether real-time interaction adds genuine value. If it does, meet. If the goal is just sharing information or recording an already-clear decision, it's a message.
Q: Isn't defaulting to messages just avoiding necessary conversations? No — it's protecting focus so the necessary conversations are better. Defaulting to async doesn't mean never meeting; it means every meeting has to justify why it needs to be live. That filters out the low-value sessions that grind people down, so the meetings that do happen are fewer and higher-value, with people actually present instead of meeting-fatigued. Teams that move fast aren't the ones that never meet — they're the ones that meet deliberately, reserving synchronous time for what genuinely benefits from it.
The meeting that should have been a message is the one that imposed the interruption tax for no real benefit. A meeting's true cost is the per-attendee time multiplied, plus the broken focus every attendee has to rebuild afterward — a bill far larger than the calendar slot suggests, and one paid in everyone's most valuable resource. Because that cost is distributed onto others, meetings get called carelessly.
The fix is to invert the default: assume a message unless something genuinely needs live interaction — debate, brainstorming, sensitive conversations, fast iteration. Make every meeting justify itself, and reserve synchronous time for the moments that truly benefit from presence. This isn't anti-meeting; it's pro-focus. Choose the channel deliberately, and you give everyone back the concentration that careless meetings quietly steal.
I spent years saving the hardest task for when I 'felt ready.' Doing it first instead quietly fixed my focus, my dread, and my output.
I tracked every distraction for a week and was horrified by what I found. Then I fixed the three that mattered most.
No following, no network, no luck. Just an unglamorous system I ran for eighteen months. Here's exactly what I did.
Comments
Sign in to join the conversation
No comments yet. Be the first to share your thoughts!