After years of sitting in meetings across different organizations, I’ve noticed a pattern that rarely gets named directly: meetings that exist primarily to avoid making a decision. Not meetings that fail to produce decisions. Meetings that are designed, whether consciously or not, to postpone them.
This is different from indecision. Indecision is a state. Meeting-as-substitute is a mechanism. It’s what happens when the friction of choosing becomes higher than the friction of convening. When a decision carries real risk, real cost, or real disagreement, a meeting can feel like progress while actually being a holding pattern.
The mechanism works because meetings have a built-in social logic. They create the appearance of movement. People gather, talk, take notes. Someone says “let’s table this and revisit next week.” Everyone nods. The meeting ends. Nothing has changed, but the group has collectively performed the act of addressing the problem. For a few hours, the pressure to decide is gone.
Why the pattern takes hold
Most organizations don’t wake up and decide to use meetings as delay tactics. It happens gradually, usually when three conditions overlap. First, the decision in question has no obviously correct answer. Second, the people involved have different priorities or risk tolerances. Third, there’s no external deadline forcing a choice.
When a decision is genuinely ambiguous, a meeting can feel like the responsible thing to do. Gather more input. Hear all perspectives. Make sure everyone’s been heard. These are reasonable impulses. But they can also become an excuse to avoid the harder work: accepting that more information won’t eliminate uncertainty, and someone has to choose anyway.
The second condition – conflicting priorities – is where meetings often become most useful as delay mechanisms. If the marketing director wants one thing and the operations director wants another, a meeting is a place where both can be heard without either having to concede. The meeting itself becomes the compromise. Everyone got their say. The status quo holds. The decision gets pushed to the next meeting.
The third condition matters more than it seems. External deadlines are brutal but clarifying. If a vendor needs an answer by Friday, a decision happens by Thursday. But many organizational decisions have soft deadlines or no deadline at all. When there’s no external pressure, the internal resistance to choosing grows stronger. A meeting becomes an acceptable way to manage that resistance without resolving it.
The cost accumulates quietly
One reason this pattern persists is that the damage isn’t immediate or obvious. A single delayed decision costs little. But organizations that habitually use meetings as substitutes for decisions pay a real price over time.
The most visible cost is velocity. Projects move slower. Initiatives stall. People spend time in meetings preparing for other meetings instead of doing work. But that’s often treated as normal – as if slowness is just how organizations operate. In reality, it’s often a symptom of postponed choices.
A quieter cost is clarity. When decisions don’t get made, people fill the vacuum with their own interpretations. Two people can leave the same meeting with completely different understandings of what was decided. This isn’t miscommunication. It’s the natural result of not actually deciding. Without a clear choice, there’s nothing to miscommunicate.
There’s also a cost to morale that’s rarely connected to its source. People get frustrated when things move slowly or when the same issues come up repeatedly in different meetings. They often blame bureaucracy or inefficiency. Sometimes they’re right. But often the real problem is simpler: a decision was never made, so the issue never actually got resolved. It just got discussed again.
How to recognize when it’s happening
The clearest signal is repetition. If the same topic appears on the agenda for the third or fourth meeting in a row, and each time the conversation is similar to the last time, a decision probably isn’t being made. The meeting is serving a different purpose – managing discomfort, maintaining the appearance of progress, or giving people a venue to restate their positions.
Another signal is the language used. Phrases like “let’s get more input,” “we need to think about this more,” or “let’s revisit this next week” can be legitimate. But when they appear consistently, and when the additional input or thinking never seems to change the underlying situation, they’re often code for “I’m not ready to choose, and this meeting is how I’m managing that.”
A third signal is the absence of a decision-maker or a decision process. If a meeting ends without anyone saying what the decision is, or how it will be made, or when it will be made, the meeting probably wasn’t designed to produce a decision. It was designed to manage the discomfort of not having one.
What happens when organizations break the pattern
I’ve seen organizations shift this dynamic, and it requires something more than just deciding faster. It requires changing what meetings are actually for. Instead of using them as forums for exploring all possible viewpoints, they become forums for executing decisions that have already been made elsewhere, or for making the final choice after the exploration is done.
This sounds simple, but it’s a real change in culture. It means accepting that some decisions will be made without full consensus. It means someone – a person or a small group – has to take responsibility for choosing, even when the choice is uncertain. It means meetings become shorter and more focused because they’re no longer doing the work of postponement.
The organizations that do this effectively usually have one thing in common: they’ve separated the work of gathering input from the work of deciding. Input happens in smaller conversations, in writing, or in asynchronous channels. Meetings happen when the decision is ready to be made. This sounds like a minor structural change, but it shifts everything. Meetings become about closure instead of exploration. They produce outcomes instead of just conversation.
What’s interesting is that this doesn’t actually make decisions better. It makes them faster. Whether they’re better depends on the quality of the input and the judgment of the person deciding. But speed itself has value. It reduces the cost of uncertainty. It prevents the accumulation of postponed choices. It allows organizations to move forward even when perfect information isn’t available.
The real work isn’t in running better meetings. It’s in accepting that some decisions will be made with incomplete information, that not everyone will agree, and that the cost of deciding is usually lower than the cost of not deciding. Meetings are useful for many things. But when they become a substitute for choice, they’re usually making things worse, not better.
