Productivity culture has a complicated relationship with meetings. We complain about them constantly, schedule them anyway, and then feel vaguely guilty when we cancel. That guilt is usually misplaced. The canceled meeting is often doing real work, in ways the attended meeting never could.
1. Canceling Forces the Question of Whether the Work Was Real
Most meetings exist to coordinate work, approve decisions, or share information. When you cancel one, the implicit question becomes: can this thing happen without the meeting? Surprisingly often, the answer is yes. The decision gets made async. The update gets written down. The blocker turns out to be unblocked already.
This is not accidental. The meeting was doing a particular kind of work, which is holding ambiguity together long enough for people to feel comfortable. When you remove that container, the ambiguity has to resolve itself. Sometimes it resolves badly, which is real signal. But often it resolves faster than the meeting would have.
Think of it like a compilation error. You can ignore a warning for months, but the moment you add a strict lint rule, the code either fixes itself (someone removes the dead branch) or the real problem surfaces. Canceling the meeting is the lint rule.
2. Attended Meetings Are Often Synchronization Theater
Synchronization, in distributed systems, is expensive. You pay a coordination cost every time you need multiple processes to agree on state. Teams do this too, and they often over-synchronize, not because it’s efficient, but because it feels responsible.
The weekly status meeting is the classic example. Everyone shows up, reads from their notes, and leaves knowing roughly what they knew before. The real purpose is social, not informational. That’s fine when the social cost of isolation is high. But in knowledge work, that same hour is often worth more as uninterrupted focus time than as shared awareness.
Paul Graham’s 2009 essay “Maker’s Schedule, Manager’s Schedule” made this argument clearly: a single meeting in the middle of the day destroys a maker’s afternoon. The asymmetry matters. Managers can absorb interruptions; engineers and writers can’t, not without a serious tax on the work that comes after.
3. The Information You Would Have Shared Is Better Written Down
Meetings are an extremely lossy medium for transmitting information. Someone talks, others half-listen while composing Slack messages, and the key decision lands in nobody’s notes. Then two weeks later someone asks what was decided and the meeting organizer reconstructs it from memory.
When you cancel and write instead, something interesting happens. You have to be precise. You can’t gesture at a concept or rely on nodding faces to tell you whether you’ve been understood. The written version becomes searchable, linkable, and asynchronously consumable by someone in a different timezone who would have missed the meeting anyway.
GitLab, which operates as a fully remote company with team members across many countries, treats written documentation as the primary medium of record, not meetings. They’ve published their internal handbook publicly. The principle isn’t “don’t talk” but rather “don’t talk when writing is more durable.”
4. Canceling Reveals Who Actually Owns the Problem
There’s a particular type of meeting that exists specifically to diffuse ownership. It has eight people on the invite, a vague agenda, and no clear decision-maker. Everyone leaves feeling informed but nobody leaves accountable.
When you cancel that meeting (or decline it), something politically uncomfortable happens: someone has to own the problem explicitly. The person who actually needs to decide something has to make a decision without the cover of collective presence. This is uncomfortable, which is exactly why the meeting existed in the first place. The discomfort is the point.
This connects to a structural issue in task management systems: systems that grow tasks indefinitely also grow meetings, because both serve as containers for unresolved ambiguity. Canceling a meeting is a kind of forcing function that your task list rarely provides.
5. The Meeting You Attend Has a Hidden Opportunity Cost
Every hour in a meeting is an hour not spent on something else. This is obvious, but the calculation is usually done wrong. People measure the cost of a meeting against doing nothing, not against the most valuable thing they could have done instead.
For a senior engineer or technical lead, the actual cost of a one-hour review meeting is often not one hour. It includes the context switch before and after, the ramp-up time needed to return to deep work, and the downstream cost if the work that got interrupted was actually on the critical path. Research from Gloria Mark at UC Irvine found that it takes around 23 minutes on average to fully return to a task after an interruption. A one-hour meeting with setup and context-switching overhead is closer to two hours of productive work displaced.
The canceled meeting doesn’t just free up calendar time. It preserves the cognitive continuity that makes the remaining time actually worth something.
6. Recurring Meetings Accrete Like Technical Debt
Technical debt accumulates when small shortcuts compound over time into structural problems. Recurring meetings work the same way. A fifteen-minute daily standup that drifts to thirty minutes, adds three new team members, becomes a problem-solving session, and never gets re-examined is technical debt with a human cost.
The right response to technical debt isn’t to feel bad about it. The right response is to audit it periodically and decide what’s worth keeping. The same applies to your recurring meetings. The one you cancel this week might have outlived its original purpose months ago. Nobody noticed because canceling feels like a statement about the team, not about the meeting.
It isn’t. The meeting you don’t need is a system running in production with no users. The professional thing to do is to shut it down.
7. Absence Teaches People to Solve Problems Without You
This one is uncomfortable, especially for people who have built their professional identity around being needed. But one of the most useful things a manager or senior individual contributor can do is make themselves absent in a structured way.
When you cancel a meeting where people expected your input, two things can happen. The team escalates (in which case the problem was genuinely load-bearing and you have real signal). Or the team solves it without you, which builds capability and reduces the number of decisions that require your presence next month. Both outcomes are more useful than attending a meeting where your presence prevents the team from ever finding out which kind of problem it was.
This is the compounding return that calendars don’t show: every meeting you skip that the team navigates without you is a small investment in a future where your calendar has more space for the problems that genuinely need you.
