The Meeting That Kills More Productivity Than It Solves

Most teams have one meeting that shouldn't exist, but everyone attends anyway.

It's usually scheduled for 60 minutes but runs 75. The organizer sends a calendar invite with no agenda, or an agenda so vague it could describe any meeting ever held. People join from their desks, their cars, their kitchen tables—some with cameras off, most half-listening while their email inbox grows. By the end, nobody can articulate what was decided, who owns what, or why they were there.

The problem isn't that this meeting is poorly run. The problem is that we've normalized meetings as the default response to uncertainty, and then we've built systems to make them easier to schedule than to cancel.

What everyone gets wrong about meeting culture

We treat meetings as the cost of doing business, like they're a tax on collaboration. The assumption is that more synchronous time equals better alignment. But the opposite is often true. A meeting that could have been an email doesn't become productive just because eight people are present. It becomes a tax on eight people's focus.

The real issue is that we've stopped asking whether a meeting is necessary before we schedule it. We ask whether it's convenient. Can everyone make Tuesday at 2pm? Yes? Then it's a go. The actual purpose—whether it could be achieved another way, whether it needs to happen at all—gets skipped.

This happens because meetings feel productive in the moment. There's the illusion of progress. People are talking. Decisions seem to be made. But the person who needed to think deeply about the problem didn't get uninterrupted time. The person who could have written a clear proposal in 90 minutes spent that time in a meeting instead. The person who had one critical question got it answered, but three other people sat through 60 minutes of irrelevance.

Why this matters more than you think

The cost of a meeting isn't the time in the meeting. It's the time before it—the mental preparation, the context-switching. It's the time after—the follow-up emails clarifying what was actually decided, because the meeting didn't produce clarity. It's the time lost to the person who needed to focus on deep work but got interrupted by a calendar notification.

Research on knowledge work shows that uninterrupted focus blocks of at least 90 minutes are when complex thinking happens. A single meeting can fragment an entire day into unusable chunks. You can't write strategy in 45-minute increments between calls. You can't solve a technical problem when you're mentally preparing for a standup in 20 minutes.

The teams that move fastest aren't the ones with the most meetings. They're the ones with the fewest meetings and the clearest written communication. They've made a choice: if it can be asynchronous, it will be. If it must be synchronous, it has a specific purpose and a time limit.

What changes when you see it clearly

Once you accept that most meetings are a default rather than a decision, you can start cutting them. Not all of them. Some meetings are essential—the ones where real-time discussion prevents misalignment, where the conversation itself generates ideas that wouldn't emerge from written exchange.

But the recurring meeting with no clear purpose? The standup that's become a status report that could be a Slack message? The alignment meeting where people are just listening to information they could read? Those are the ones killing your productivity.

The teams that protect their people's focus time don't do it by accident. They do it by treating every meeting as something that needs to justify its existence, not something that justifies itself by existing.

Start with one meeting. The one everyone dreads. Ask: what would happen if we didn't have this? If the answer is "nothing," you've found your answer.