If you cannot articulate what will be decided, the meeting has no reason to exist.
Not an update. Not a brainstorm. Not a check-in. A decision — named, scoped, and owned before anyone opens a calendar invite. If you cannot articulate what will be decided, the meeting has no reason to exist.
"The moment you allow a meeting to exist for 'discussion,' you have already decided nothing will happen."
Most meeting invites describe a topic. Topics are not decisions. "Q4 strategy" describes a subject area. "Product roadmap review" describes an activity. "Syncing on the client situation" describes a social ritual. None of these tell a participant what will be different about the world at the end of the next sixty minutes — because the person who called the meeting hasn't answered that question themselves.
This is not carelessness. It is habit. Organizations have trained themselves to equate discussion with progress. They have not. Discussion is the input. A decision is the output. And organizations that cannot distinguish between the two are running on the illusion of momentum.
The anatomy of a real meeting purpose
A meeting that earns its place can be described in one sentence containing three elements: a verb that commits to a decision, a scope that makes the decision finite, and a deadline or context that makes the decision urgent. Remove any one of these and you have a topic — not a meeting purpose.
A committing verb
Decide. Choose. Approve. Reject. Prioritize. Select. Commit. Not: discuss, review, align, explore, share, touch base, or sync. The verb tells the room what it is authorized to produce.
A finite scope
A named decision, not a category. Not "product strategy" — but "which of three pricing models to launch in Q1." If a meeting contains multiple decisions, each one must be individually scoped.
A reason it matters now
What happens if this decision slips another week? If the answer is "nothing much" — it is not urgent enough to convene. Urgency is not manufactured. It is either real or it isn't.
One named owner
Every decision requires someone who will be accountable for what happens next. The meeting purpose should make clear whose judgment carries the room. If it's "the group," no one owns it.
From topics to decisions — before & after
The shift from a topic to a decision is often a single verb. Below: the same meeting rewritten. The left column describes what will happen in the room. The right column describes what will leave it.
Q4 marketing strategy
Which two channels to invest in for Q4, given the budget reduction
Product roadmap
The proposed feature freeze date, so engineering can begin sprint planning Monday
The client situation
Whether to extend the contract, renegotiate terms, or exit — and name the person who sends the response
Hiring pipeline
Which of the three finalists to move to offer, before the competing offer expires Thursday
Options for the office expansion
Between renewing the current lease or moving to the new location — so legal can respond by Friday
Engineering priorities
The top three items for the next sprint from a list of nine, owned by the engineering lead
Defined means named — every single one
The default should be one meeting, one decision. A room that knows it has one thing to do is a room that does it. But the real world includes roadmap prioritization sessions, hiring panels, incident reviews, and architecture tradeoffs — meetings where multiple related decisions are genuinely more efficient together than apart.
The principle is not "one decision per meeting." It is "zero unnamed decisions per meeting." A roadmap session with five prioritization calls is fine — as long as each one is listed on the agenda beforehand, individually scoped, time-boxed, and assigned an owner. What is never acceptable is a meeting that starts without a single named decision. That is not a meeting. It is a habit.
"The discipline is not counting decisions. It is naming them. An unnamed decision is an unmade decision — regardless of how long the room talked."
When a meeting does carry multiple decisions, the bar is higher, not lower. Each decision needs its own time allocation, its own owner, and its own exit criteria. If any decision on the list cannot clear that bar, it does not belong on the agenda — it belongs in a document or a separate meeting. The goal is not fewer decisions per meeting. It is zero unnamed ones.
Framework tool
The One Decision Test
Describe your next meeting in plain language. The tool will assess whether it contains a real decision — and if not, reframe it into one.