Most meetings produce updates. A few produce decisions. The difference is not the people in the room. It is the design of the room.
1. The default meeting is an update loop
Someone shares status. Others respond with questions or additions. The meeting ends. No decision was made. A follow-up is scheduled to make the decision that should have been made here.
This is not laziness. It is what happens when meetings are not designed to decide.
An update loop has its place, but it is not a decision vehicle. When you run it as one, you get movement without closure.
2. Why decisions don't happen in meetings
The decision is not named going in. Most meeting invites describe a topic. Not a decision. There is a difference. "Discuss Q3 roadmap" is a topic. "Decide which two initiatives get cut from Q3" is a decision. One produces conversation. The other produces an outcome.
The decision-maker is not identified. In many rooms, everyone has a view. No one has the call. Discussion runs until time expires. The meeting ends with "let's align offline." Nothing is aligned offline.
The options are not prepared. Good decisions require options with trade-offs laid out in advance. Most meetings arrive at the decision point with raw information, not structured choices. The room then spends its time building the options instead of choosing between them.
The cost of not deciding is invisible. Postponing a decision feels safe. It rarely is. But because the cost lands later — in delay, rework, or lost time — it is not felt in the room. The meeting ends without consequence. The pattern repeats.
3. What a decision meeting requires
A named decision. One sentence. Written in the invite. Not "discuss" — decide. Not "review" — choose.
A named decision-maker. One person. Stated in advance. Others inform. One person calls it.
Prepared options. Two or three. With trade-offs. Circulated before the meeting. Not built inside it.
A time boundary. Fixed. Stated at the start. "We have 30 minutes. We leave with a decision."
A written output. The decision, the rationale, the owner, the next action. Not meeting notes. A decision record.
4. The operator's job in the room
The operator does not wait for a decision to emerge. They design the conditions so a decision is unavoidable.
Before the meeting: name the decision, prepare the options, identify who calls it. In the meeting: move through context fast, surface the real trade-off, hold the room to the decision point. After the meeting: write it down, distribute it, make sure it does not dissolve into ambiguity by end of day.
The room will drift toward discussion. The operator pulls it back to the decision. The room will avoid the hard trade-off. The operator names it. The room will leave without closure. The operator does not let that happen.
5. When to not call a decision meeting
Not every decision needs a meeting.
If one person can make it — they should. No meeting needed. If the information is not ready — wait. A meeting without prepared options is a discussion with a timer. If the decision-maker is not in the room — reschedule. A meeting without authority is theater.
The most effective operators cancel more meetings than they run. They call a meeting when a decision needs a room. Not before.
Conclusion
The meeting is not the problem. The absence of design is.
A well-designed decision meeting is short, uncomfortable, and productive. It ends with something written down that did not exist when it started.
Most meetings are a group of people waiting for someone to decide. A decision meeting is a room designed so that waiting is not an option.