Why the Unnecessary Meeting Keeps Surviving

Opening Observation

There is a particular kind of meeting most professionals can identify within seconds of joining. The agenda is informational. The content could be written down. The discussion, if it happens, is surface-level. Afterward, someone will say what everyone was already thinking: that could have been a document.

And yet, when next week arrives, the meeting is still on the calendar. Same time, same room, same format. I've seen this pattern repeat across several organizations, in different industries, at different levels of seniority. The meeting that should be a document has remarkable staying power. The question worth exploring is why.

The Pattern

The pattern is not really about meetings versus documents. It is about how organizations handle the transfer of information when trust and accountability are unevenly distributed.

When someone sends a document, they lose control of the experience. They cannot confirm who read it. They cannot gauge reactions in real time. They cannot course-correct if something is misunderstood. The meeting gives them all of that. It is a controlled environment for information transfer, and more importantly, it produces a visible event that signals the information was shared.

On the receiving side, the meeting also serves a purpose. It removes the obligation to engage on your own time. You show up, you absorb what you can, and the calendar block serves as evidence of participation. The document, by contrast, asks more of you. It asks you to read carefully, to flag concerns asynchronously, and to be accountable for what you did or did not absorb.

So the meeting persists not because it is the best format. It persists because it is the lowest-friction format for both sides, given the actual trust levels in the organization.

📌Note

If the organization cannot trust that people will engage with written updates—or hold them accountable when they do not—the meeting becomes the safety net for everyone involved.

Why It Happens

Several dynamics keep this cycle in place.

First, there is a deep discomfort with asynchronous silence. When a document is shared and nobody responds, the sender has no idea what that means. Agreement? Indifference? Nobody read it? In a meeting, even a quiet nod or a clarifying question provides signal. Organizations that run on synchronous feedback loops find it genuinely difficult to operate any other way.

Second, meetings create a sense of shared accountability that documents do not. "We covered this in the Thursday sync" carries more organizational weight than "I sent a memo on Tuesday." The meeting becomes a ritual of collective acknowledgment.

Third, there is a calendaring incentive at play. In many organizations, a full calendar signals relevance. Canceling recurring meetings can feel like surrendering organizational presence, especially for middle managers whose influence is partly tied to the forums they convene.

The Leadership Lens

From a leadership perspective, the interesting question is not whether a specific meeting should be a document. That is a tactical call anyone can make. The harder question is what it means when an organization cannot make that swap.

If your teams consistently default to meetings for information that could be written, that tells you something about the underlying operating environment. It may signal low confidence that written communication will be read and acted on. It may reveal that accountability structures depend on synchronous witness rather than individual ownership. It may simply reflect that nobody has established clear norms around when each format is appropriate.

I've watched this play out differently across organizations. In some, a senior leader modeling strong asynchronous communication, writing clearly, expecting written responses, making decisions based on documents, shifted the culture within months. In others, the meeting culture was so deeply embedded that even explicit mandates to reduce meetings barely made a dent. The meetings just got shorter or renamed.

Practical Takeaway

A few observations from watching this dynamic over the years:

The swap from meeting to document only works when there is a credible consequence for not engaging with the document. Decisions have to move forward based on what was written, and silence has to be treated as consent.
Notice who resists the shift most. The resistance frequently comes from those whose organizational relevance is tied to convening others. Removing the meeting can feel like removing their function.
The goal is not zero meetings. Some discussions genuinely benefit from real-time exchange. The goal is honesty about which meetings exist for communication and which exist for coordination.

The unnecessary meeting survives because it is doing more than sharing information—it is compensating for missing systems of trust, accountability, and written engagement.

Closing Reflection

The next time you sit through a meeting that could have been a document, it might be worth asking a different question than the usual one. Instead of wondering why this is a meeting, consider what would have to be true about your organization for the document to actually work instead. The gap between those two states often reveals more about the operating culture than any engagement survey will.