A meeting appears on the calendar because someone needs something and cannot get it through the systems around them.
They need a decision, so they invite everyone who might object. They need information, so they ask people to say it out loud. They need alignment, so they gather teams that have been working from different assumptions for three weeks. They need accountability, so they create a room where responsibility can be shared before anything goes wrong.
That is why meetings feel pointless. They are often scheduled when the organization does not know how to coordinate without synchronous group time.
The meeting inherits the failure of the surrounding system, then gets blamed for being boring.
What the Meeting Is Compensating For
A project lead schedules a thirty-minute sync because the release date is unclear. The engineering tracker says one thing. The launch plan says another. The customer-facing date lives in a sales deck. No single artifact can be trusted, so the project lead pulls people into a call and asks for the current state.
That meeting is doing the work of documentation.
Another team schedules a stakeholder review to choose between two product options. Everyone attends because no one is sure who owns the decision. The person with the most authority asks for opinions, hears six partial perspectives, and ends the meeting by saying the team should gather more input.
That meeting is doing the work of decision authority.
A director schedules an alignment meeting because two teams keep making incompatible plans. One team is optimizing for enterprise readiness. The other is optimizing for activation. Both are behaving rationally inside the incentives they were given. The meeting asks them to negotiate the conflict one hour at a time.
That meeting is doing the work of shared priorities.
A conflict review appears after a missed dependency. The teams involved explain their timelines, their assumptions, and the messages they sent. Everyone is polite. The organization never changes the incentives that made the dependency easy to miss.
That meeting is doing the work of an operating system the company has not built.
Accountability Gets Spread Around
Meetings are useful when accountability feels dangerous.
A manager who makes a call alone owns the result. If the call fails, the reasoning can be inspected. The decision has an author. That clarity is efficient, and in many organizations it is also risky.
A meeting distributes the risk. Stakeholders were consulted. Concerns were heard. The decision followed process. If the outcome fails, the failure belongs to the group, or to the process, or to the information available at the time. The room becomes a kind of insurance policy.
This explains a particular category of pointless meeting: the decision is obvious before the call starts, but the call still happens because making it alone would expose someone. The meeting does not improve the decision. It gives the decision a wider surface area.
Risk-averse organizations accumulate these meetings quickly. People learn that being wrong in a meeting is safer than being wrong in a document with their name attached. The calendar fills with consensus rituals because judgment has become expensive to show.
The Cost Is Larger Than the Calendar Block
A one-hour meeting with eight people costs eight person-hours before anything else is counted. That number is already high, but it is still too neat.
The meeting interrupts whatever each person was doing before it. Engineers lose the local state of the code they were holding in their head. Designers lose the comparison they were making between flows. Product managers lose the thread of a customer pattern they were writing down. After the meeting, everyone spends time reconstructing the work they left.
Preparation adds another layer. If eight people each spend half an hour preparing for a one-hour meeting, the visible calendar block is only part of the expense. The organization has now bought a twelve-person-hour event, plus the recovery time around it, to produce whatever happened in that room.
Sometimes that trade is worth it. A hard decision, a real negotiation, or a production incident review can justify the synchronous cost. Many meetings spend that cost on information transfer that could have been written once and read selectively.
The waste is easy to miss because the calendar shows duration, not recovery time, preparation time, or the work that would have happened in the same uninterrupted stretch.
Calendar Defaults Become Meeting Design
Most meetings last thirty or sixty minutes because the scheduling tool makes those durations easy.
The work rarely fits those blocks exactly. A decision might need twelve minutes if the options are clear. An incident review might need ninety if the timeline is still contested. A status update might need no meeting at all. The calendar offers standard shapes, and the work is poured into them.
Once the block exists, the meeting expands. A twenty-minute agenda fills thirty minutes. A decision reached early gets revisited because there is still time. Someone raises a related topic. Someone asks a question that would have been fine in a comment thread. The meeting consumes the container it was given.
Ending early requires a small act of authority. Someone has to say the purpose has been met and the remaining time should go back to the people in the room. In cultures where meetings carry status, that can feel abrupt. In cultures where busyness signals importance, returning time can make the meeting look underprepared.
So the last fifteen minutes become drift.
Meetings Carry Status Signals
The attendee list often says as much as the agenda.
Being invited signals relevance. Being excluded signals distance from the work, even when exclusion would be a gift. Senior people attend meetings to show interest or oversight. Managers invite broad groups to show that a topic matters. People accept invitations because declining can look like disengagement.
A coordination problem that needs three people for fifteen minutes becomes twelve people for an hour because the meeting also has to demonstrate inclusion. Each added person slightly increases the cost, slightly changes the conversation, and slightly increases the chance that someone else should be invited for balance.
The meeting begins to serve two functions at once. It coordinates the work, and it displays who is close to the work. The display function usually wins because it is socially visible in a way efficient coordination is not.
This is why attendee lists grow and rarely shrink. Once a person or function has been included, removal creates meaning. Keeping them included only creates cost, and cost spread across many calendars is easy to ignore.
False Consensus Feels Like Alignment
A group reaches the end of a meeting. Someone proposes the path forward. A few people nod. No one objects with enough force to stop it. The organizer writes down the next step and everyone leaves believing the room aligned.
Then implementation starts.
Engineering treats the path as provisional because two risks were unresolved. Marketing treats it as committed because the date was repeated three times. Support waits for more detail because no customer messaging was agreed. Product assumes scope can still move because no one explicitly rejected that option.
The meeting produced agreement-shaped silence.
Public disagreement has a cost. It extends the meeting. It can put a person in conflict with someone more senior. It requires turning a half-formed concern into a coherent argument in front of the room. Many people choose to stay quiet, especially when the decision seems only partly connected to their work.
That silence becomes expensive later. The organization discovers the disagreement during execution, when changing direction costs more and blame has somewhere to land.
The Meetings That Earn Their Keep
Some coordination work does need a room, or at least a live call.
Negotiation often benefits from synchronous discussion because each party adjusts to the other’s constraints in real time. Conflict resolution can need the same immediacy, especially when written messages have already hardened positions. Architectural decisions sometimes require a fast exchange of trade-offs where one answer changes the next question.
Complex explanation can also justify a meeting. A production incident walkthrough, a new system architecture, or a migration plan may need live clarification because the first version of the explanation will expose gaps. The meeting is useful when the questions improve the shared model faster than a document thread would.
Remote teams also need deliberate social contact. A purely social meeting can be legitimate because its purpose is connection. The problem starts when organizations pretend social maintenance, status reporting, decision-making, and information transfer are the same kind of event.
They require different tools.
What Replaces the Pointless Ones
Information transfer needs durable writing. The document does not have to be grand. It has to be clear, findable, and current enough that people stop calling meetings to reconstruct facts by voice.
Decision-making needs named authority. One person or group owns the call, gathers input, documents the reasoning, and communicates the result. A meeting may still happen, but it has a decision owner and a decision to make before anyone joins.
Status needs instrumentation. If people have to speak routine progress into a room every week, the work is probably not visible where it happens. Trackers, dashboards, release notes, and short written updates are less dramatic than live status rounds. They are also easier to inspect without spending eight calendars at once.
Alignment needs shared context before the conflict arrives. Teams need to know the priorities they are optimizing for, the boundaries they can move inside, and the places where another team depends on them. A recurring meeting can surface misalignment, but it cannot substitute for the operating context that would have prevented it.
These systems take work. Writing well takes time. Clear authority creates accountability. Dashboards require instrumentation. Shared priorities require leadership to make trade-offs explicit before teams collide.
Scheduling a meeting is easier, which is why organizations keep doing it.
Why the Culture Holds
Meeting culture persists because the person who schedules the meeting usually receives the most immediate benefit. They get information, input, visibility, a decision-shaped conversation, or shared accountability. The cost lands across everyone else’s calendar in small enough pieces to seem tolerable.
Each individual meeting can be defended. This stakeholder should be consulted. That dependency should be discussed. This update would be clearer live. That decision would benefit from alignment. The aggregate result is a week with no room left for the work all those meetings are supposedly coordinating.
Then the organization schedules a meeting about meeting culture.
People discuss better agendas, shorter defaults, optional attendance, and clearer owners. Everyone agrees the calendar has become unreasonable. The meeting ends with sensible norms and no change to the systems that made the meetings necessary.
The pointless feeling comes from that mismatch. People sit in meetings that are formally about coordination and can feel, with irritating accuracy, that the real work is somewhere else: in the missing document, the unnamed decision owner, the unresolved priority conflict, or the dashboard no one built.
A meeting can be a useful operating tool. It becomes expensive theater when it is asked to compensate for every missing part of the organization around it.
