The Productivity Credit You Never Claim
You’ve had this experience. You clear an afternoon of back-to-back meetings, mostly out of exhaustion, and by the end of the day you’ve shipped something real. A document drafted, a problem solved, a decision actually made. You feel a little guilty, like you abandoned your obligations. But the work is done.
The guilt is misplaced. What you did was correct. The meetings you skipped almost certainly would have produced less than the focused work you completed instead. And the fact that this still feels counterintuitive, even to people who know better, is worth examining carefully.
This isn’t an argument for ignoring your colleagues or opting out of coordination entirely. It’s an argument for taking seriously what meetings actually cost, what they reliably produce, and why the calculus almost always favors fewer of them than you’re currently attending.
What Meetings Are Actually For
Meetings are good at exactly two things: building shared understanding quickly, and making decisions that require negotiation between parties who have different information. That’s it. If you’re not doing one of those two things, you are in the wrong format.
Statusupdates don’t require meetings. Brainstorming rarely requires a room (and research consistently shows that individual ideation produces more and better ideas than group brainstorming, due to social loafing and anchoring effects). Presentations don’t require meetings. Neither do announcements. These things use the meeting format, but they are not meetings in the functional sense, they’re performances with an audience.
When you look at your calendar through this lens, you start to notice how many of your meetings are actually performances. Someone is presenting a status. Someone is explaining a decision already made. Someone is “aligning” a group on information that could have gone in a document. These gatherings feel collaborative because everyone is in the room together, but the work isn’t happening there. The work happened before the meeting, or it will happen after, or it won’t happen at all.
The Fragmentation Problem Nobody Tracks
The direct cost of a meeting is visible: one hour, five people, five hours of collective time gone. But the indirect cost is what really compounds.
Calendar Tetris fragments your day into blocks too small to do anything real. A researcher at UC Irvine, Gloria Mark, has published extensively on attention and interruption, and her work demonstrates that it takes significant time after an interruption to return to deep work. A 30-minute meeting inserted into the middle of your afternoon doesn’t just cost 30 minutes. It effectively destroys whatever focus-intensive work might have occupied the surrounding hours.
Knowledge work, almost by definition, requires sustained thinking. Writing, coding, designing, analyzing, deciding on complex problems: all of these require you to hold a lot of context in your head simultaneously. Every interruption drops that context. You spend the first part of each work session rebuilding it. If your day is fragmented into 45-minute blocks by meetings, you may technically have six hours of “free time” on your calendar while doing almost no deep work at all.
This is the hidden tax that never shows up in meeting ROI calculations. You don’t just lose the time in the meeting. You lose the time around it.
Why You Kept Attending Bad Meetings
There’s a social logic to meetings that overrides their functional logic. Attending signals engagement. Missing signals disinterest, or worse, insubordination. The person who declines a meeting invite is making a statement, even when the meeting genuinely didn’t need them.
Organizations reinforce this by measuring presence rather than output. In many workplaces, the person who attends every meeting looks more dedicated than the person who skips meetings to ship work. This creates a perverse incentive: you get socially rewarded for showing up to things that slow you down.
There’s also what you might call the Fear of Missing Out on Decisions, or FOMOD. Meetings are where decisions sometimes get made informally, where someone offhand says “let’s just do X” and everyone nods. If you’re not there, you might find yourself bound by a decision you had no input on. So you attend, not because you have something to contribute, but because absence feels like risk.
Both of these pressures are real. They’re also problems worth fixing rather than accommodating. The task you keep postponing because it never feels as urgent as a calendar invite is often the work that actually matters.
What Actually Happens When You Cancel
Here’s what you tend to find when you start protecting your calendar deliberately. The work that felt like it required a meeting often doesn’t. When you send a document instead of scheduling a review, people read it asynchronously and leave better comments than they would have made on the spot. When you cancel a check-in and ask for written updates instead, you get more thoughtful answers. When you decline a brainstorm and ask people to send ideas beforehand, you get more ideas, not fewer.
This isn’t a coincidence. Writing forces clarity in a way that speaking doesn’t. When someone has to articulate a problem in writing, they often solve part of it in the act of writing it down. The meeting, which would have involved them describing the problem out loud to you for twenty minutes, gets replaced by a paragraph that already contains half the answer.
The meetings that survive this filter, the ones where something genuinely requires real-time negotiation or collective sense-making, tend to be shorter and more productive. When you stop having meetings by default, the ones you do have carry more weight. People come prepared because there’s no filler to coast through.
How to Start Fixing Your Calendar
The goal isn’t zero meetings. The goal is intentional meetings. Here’s a practical approach to get there.
Audit before you cancel. Look at every recurring meeting on your calendar and ask: what decision or shared understanding does this produce that couldn’t happen asynchronously? If you can’t answer that, the meeting is a candidate for elimination or replacement. If you find yourself struggling to identify what a meeting actually produces, that’s a sign it was probably already broken.
Replace before you remove. Don’t just cancel things cold. When you remove a recurring check-in, replace it with a lightweight async alternative: a weekly written update, a shared doc, a Slack thread with a standing prompt. This reduces the social friction of canceling and often produces better information anyway.
Protect blocks, not just hours. Having four free hours on your calendar doesn’t help if those hours are split across the day by meetings. What you need is two to three unbroken hours where you can do actual work. Treat those blocks like appointments. Decline meetings that would break them unless the meeting passes the sniff test for real-time necessity.
Distinguish your presence from your input. For meetings where you have relevant input but don’t need to be present for the full discussion, offer to contribute in advance. Send your thoughts, your data, your recommendation. Ask to be looped in on the outcome. You’re not abandoning the process, you’re participating more efficiently.
Create a default of documents. When someone wants to schedule a meeting with you, try asking first: can you send me what you’re thinking about, and I’ll respond by end of week? About half the time, this replaces the meeting entirely. The other half, it makes the meeting much shorter because the context work is already done.
The Organizational Angle
If you’re in a position to influence how your team works, the stakes here are higher than your personal calendar. Meeting culture is one of the few areas where individual bad habits compound into structural dysfunction. One person who schedules meetings instead of writing things down creates obligations for five others. Those five people, fragmented and reactive, start scheduling their own meetings to compensate for lost coordination. The load multiplies.
Teams that default to written communication tend to build something valuable over time: a record. Decisions are documented. Reasoning is preserved. New people can understand context without interrogating veterans. The knowledge that accumulates in meeting rooms evaporates; the knowledge that accumulates in documents is searchable.
This is a real competitive advantage, even if it’s slow to develop. A team that makes decisions in documents can scale its decision-making as it grows. A team that makes decisions in meetings gets slower as it adds people, because more people means more coordination overhead, which means more meetings, which means more fragmentation.
What This Means
The meeting you canceled didn’t just save you an hour. It gave you a block of context-rich focus time, forced whoever would have run it to articulate the problem in writing instead, reduced the pressure to fill silence with non-decisions, and left a paper trail of actual work rather than a memory of discussion.
None of this requires radical calendar reform. Start small: audit one recurring meeting this week. Ask what it actually produces. Offer an async alternative. See what happens. The answer, most of the time, is that the work continues without it, and often improves.
Your calendar is a representation of your priorities. If it’s full of other people’s meetings, it’s a representation of their priorities. That’s fixable, but only if you start treating cancellation as a legitimate act of professional judgment rather than a social failure.
