The Meeting That Could Have Been a Slack Message

Most organizations have stopped asking whether they have too many meetings. They've accepted it as inevitable—the cost of doing business at scale. What they haven't accepted is that the problem might be structural, not circumstantial.

The real issue isn't that meetings exist. It's that meetings have become the default communication mechanism for things that require no synchronous discussion whatsoever. A status update. A decision that's already been made. Information that could live in a document. These don't need bodies in a room, virtual or otherwise. Yet they consume roughly 23% of the average knowledge worker's week, according to most surveys that measure this sort of thing. That's not a scheduling problem. That's a decision-making problem.

Here's what everyone gets wrong about meeting culture: they think the solution is better meeting hygiene. Shorter agendas. Fewer attendees. No cameras on Fridays. These are optimizations of a broken system. They're like rearranging deck chairs on a ship that shouldn't have left port.

The real dysfunction runs deeper. Meetings have become a proxy for visibility. Managers schedule them because they need to see work happening in real time. Teams attend them because not showing up signals disengagement. Organizations hold them because the alternative—trusting people to work asynchronously—requires a level of documentation and clarity that most companies have never developed. So instead of building that muscle, they just add another meeting.

This matters more than it appears on the surface because it fundamentally changes how work gets done. When your default is synchronous communication, you optimize for people who are available right now. You disadvantage anyone in a different timezone, anyone with caregiving responsibilities, anyone whose best thinking happens at 11 PM instead of 2 PM. You also create a culture where visibility equals value—where the person who speaks loudest in the meeting gets credit for the idea, regardless of who actually developed it.

But there's something else happening too. Meetings create the illusion of progress. You leave a meeting feeling like something happened. A decision was made. A problem was solved. Except often, nothing was actually decided—you just scheduled a follow-up meeting. The problem wasn't solved; it was discussed. And the decision will be revisited in the next sync because someone wasn't there, or someone changed their mind, or someone realized the information they needed wasn't in the room.

What actually changes when you see this clearly is your relationship to asynchronous work. Not as a second-class alternative to "real" meetings, but as the primary mode of operation. This means writing things down. Thinking before you communicate. Giving people time to respond without the pressure of real-time conversation. It means trusting that good ideas don't need to be defended in the moment—they can be evaluated on their merits.

This also means accepting that some decisions will take longer. Not because people are slower, but because they're more thorough. Someone in Singapore can read your proposal and add context you wouldn't have gotten in a meeting. Someone who's introverted can contribute their best thinking instead of being talked over. Someone who needs to think in writing instead of speaking can actually participate.

The companies that have figured this out—the ones that have genuinely reduced meeting load without sacrificing coordination—didn't do it by being more efficient with meetings. They did it by being more intentional about when synchronous communication is actually necessary. A brainstorm where you need rapid-fire ideation? That's a meeting. A status update? That's a Slack message. A decision that affects multiple teams? That's a document with comment threads, not a calendar invite.

The meeting that could have been a Slack message isn't a joke about poor communication. It's a symptom of an organization that hasn't decided what synchronous time is actually for. Until you answer that question, you'll keep scheduling meetings to discuss why you have too many meetings.