You’ve felt it before. You cancel a meeting, half-guilty, expecting the afternoon to drift into nothing. Then something unexpected happens: a decision gets made in a Slack thread, a doc gets written, someone figures out the problem on their own. Nobody misses the hour. The work, somehow, still moves.
This isn’t an accident, and it’s not luck. There’s a structural reason why the meeting you cleared from the calendar often does more productive work than the one you sat through. Understanding that reason changes how you schedule your week.
Meetings Solve the Wrong Version of Every Problem
Most meetings exist to resolve uncertainty. Someone doesn’t know something, or two people disagree, or a decision needs to be made. The meeting is supposed to be the mechanism that produces clarity.
But meetings don’t actually produce clarity. They produce conversation, and then the clarity has to be extracted from that conversation afterward. You’ve been in meetings where the answer was obvious to everyone in the room 20 minutes before it ended. The remaining time was spent on confirmation, on social ritual, on making sure nobody left feeling unheard. That’s not wasted time in a social sense. It is wasted time in a productivity sense.
When you cancel the meeting, you force a different mechanism. Whoever needs the decision has to either figure it out themselves or ask a targeted question in writing. Writing forces the problem to become specific. “I need input on the Q3 roadmap” (a meeting premise) becomes “Should we prioritize the API redesign or the onboarding flow given that we have three engineers available?” (an answerable question). The specificity does a lot of the cognitive work the meeting was supposed to do.
Synchronous Time Has a Hidden Multiplier
Here’s the math that rarely gets done. A one-hour meeting with five people doesn’t cost one hour. It costs five hours of individual attention, plus the transition cost on either side as each person switches out of deep work and then back into it. Research on attention and task-switching consistently shows that recovery time after an interruption runs longer than the interruption itself. So a one-hour meeting for five people might realistically cost eight or nine hours of productive capacity across the team.
This is why the ghost meeting that haunts every sprint is such a familiar problem. The meeting you cancelled this week is the only meeting whose hidden cost you actually avoided.
When you cancel and the work still gets done, what you’re observing is that the task’s real cost was lower than the meeting’s cost. The async alternative (a doc, a Slack thread, a quick voice memo, a shared comment in Figma) consumed less collective attention and produced a comparable output. Not always, but often enough to be worth testing.
When Meetings Actually Earn Their Cost
This isn’t an argument for eliminating meetings. Some problems genuinely need synchronous, high-bandwidth conversation. If you’re navigating an interpersonal conflict, ambiguity requires real-time emotional calibration that text handles poorly. If you’re brainstorming in a domain where ideas need to collide and build on each other quickly, a good working session can outperform days of async back-and-forth. If someone is new to a team or new to a problem, live conversation builds shared context faster than documentation.
The tell is whether the meeting is designed around exchange or around updates. Updates should almost never require a meeting. Exchange, debate, and genuine co-creation sometimes should. If you look at your next week’s calendar and classify each meeting by which category it falls into, you’ll probably find the split isn’t close.
The meetings worth keeping tend to have three things in common: a specific decision or output that only the group can produce, a tight participant list (anyone who doesn’t actively contribute to the output shouldn’t be there), and a defined ending point that isn’t the scheduled end time but the moment the output is produced.
How to Build a Default Toward Canceling
The practical change isn’t dramatic. You don’t need to blow up your calendar or implement a no-meeting policy. You need to raise the bar for what earns synchronous time.
Start with a simple pre-meeting question you ask yourself (or the organizer): what is the specific output of this meeting, and why can’t that output be produced asynchronously? If you can’t answer the first part, the meeting isn’t ready to happen. If you can’t answer the second part, the meeting probably shouldn’t happen.
For recurring meetings, apply a version of the same test quarterly. Many recurring meetings were scheduled to solve a problem that no longer exists. They persist because canceling feels like a statement, and nobody wants to make the statement. Make it anyway.
If you’re a manager, the most useful thing you can do is model aggressive async defaults on anything that doesn’t require live exchange. Write the decision in a doc and ask for comments. Record a short walkthrough video instead of scheduling a sync. Send the question in Slack with a 24-hour response window before deciding a meeting is necessary. Your team will follow the pattern.
What the Cleared Space Actually Produces
The thing nobody tells you about canceled meetings is that the value isn’t just time saved. It’s also signal received. When you cancel a meeting and watch what happens, you learn something about the meeting’s original function. If the work gets done in a Slack thread, the meeting was an update. If a decision gets stuck and nobody makes it, you’ve found a real coordination problem that a well-designed process (not more meetings) can fix. If the decision gets made wrong and needs to be revisited, you’ve learned that this particular kind of decision actually needs live conversation.
The canceled meeting becomes a diagnostic. Over time, you build a much clearer sense of which problems in your organization genuinely require synchronous time and which ones have just defaulted to it out of habit.
Your calendar isn’t a measure of your output. The space you protect in it is.
