A meeting is a gathering to deliberate. By the name, the emphasis belongs on deliberation rather than gathering — yet most conference rooms weight gathering-and-sharing above deliberating-and-deciding. When that distinction collapses, meeting design stops working and time drains away.
"What Did You Gather to Decide Today?"
From a coaching conversation with a division head. He pushed a thick stack of meeting materials across the table.
"This is this week's regular meeting deck. As you can see, we're not short on data. Every team pulls this carefully — but somehow the meeting always runs past two hours. Would tidying the materials help?"
"The materials look sufficient. Let me ask the reverse: at that meeting this week, what did you gather to decide?"
"Hm… not so much decide as share each team's status and discuss issues if any come up. Isn't that what these are?"
It sounds natural, and plenty of meetings run exactly that way. But "a place to share and discuss" quietly omits what's actually being decided.
A Meeting Has One of Two Purposes
You call a meeting to inform or to decide. The two are entirely different in character.
Informing is one-directional and rarely needs everyone's time simultaneously. If it must take meeting form, the subject should be one that genuinely requires face-to-face delivery to avoid misunderstanding.
Deciding requires multiple people's judgment and accountability in one place. Views have to be exchanged, an agenda item has to surface, and it has to carry through to an actual decision.
A meeting is an expensive device that ties up many people's time at once. The moment you say "let's all share and discuss," that expensive format goes to the cheaper job. And informing has no natural end — there's always more data to cover and another issue to add, so the meeting stretches.
Meetings don't run long because there's too much material or too little time to share. They run long because nobody decided what, how and why before setting the attendees and the date.
Most Companies Hold "Gathering Meetings," Not "Deciding Meetings"
This isn't one facilitator's laziness. It's organizational, structural and habitual. Three signs:
First, look at why the meeting exists. Most meetings happen because they're recurring, not because something needs deciding. Weekly meetings, monthly reports and standing check-ins sit in the calendar, so the slot arrives whether or not there's an agenda. The agenda doesn't summon the meeting; the meeting hunts for an agenda.
Second, materials point toward reporting. What each team pulls is oriented around demonstrating how much they did. The message "so what needs deciding, and what discussion does it require" is missing. So people look at raw data together for the first time in the room, improvised analysis begins, and the meeting ends mid-analysis — or never gets past sharing.
Third, it deepens as companies grow. In a small organization, things get decided at the next desk. As headcount grows and departments split, meetings that "invite everyone related" multiply. Unrelated people sit as audience, the meeting becomes a place to be briefed rather than to decide, and conclusions recede as attendance rises.
It also appears inverted: a meeting labeled a decision meeting where nothing gets decided, because the decision-maker isn't present or no judgment criteria exist. Opinions surface; the conclusion becomes "let's look further and decide next time." Opposite direction, same root — nobody established shared understanding of the purpose beforehand.
How to Change It
1. Set the purpose first. Before any meeting, decide whether it informs or decides, choose attendees accordingly, and circulate the relevant material in advance.
2. Write today's decision as one sentence. "By end of week, choose option A or B for next quarter's budget allocation." A surprising number of meetings can't produce that line. If it won't write, this isn't a decision meeting — and you may not need to hold it.
3. Split what to share from what to decide. Status briefings, department updates and reference metrics go out before the meeting as a document or channel post. The meeting keeps only the analysis, questions, options and judgment criteria the decision requires.
4. Derive attendees from that. Not everyone related — only the people participating in the decision and those holding the experience, knowledge or data the judgment needs. Many companies notify attendees before working out the details, which is exactly why people arrive resentful.
5. Leave a result behind. If what, who and by when aren't tangible by the end, close the meeting and schedule the next. That closure keeps this meeting from stretching further while acknowledging that the inputs — or the group's readiness — aren't sufficient yet.
Materials Change Direction Too
Meeting materials aren't for spreading out and hunting for something to decide. They should be built to support a judgment you defined in advance.
Occasionally teams format materials as a menu so the decision-maker can simply pick. That's the pattern to avoid most: it offloads all accountability onto the leader, and inverted, it says nobody else in the room wants to carry any.
Defining meeting types, procedures and formats — and teaching them to the leadership group — is ultimately the organization's job. Most companies have no formal meeting manual, or one that exists in name only, and even as inefficiency accumulates nobody raises it. It's clearly a problem that goes untreated as one.