A decision meeting needs three things: a single decider, a question that can be answered with a yes, no, or A-or-B, and a closing line that names the action, owner, and date. Cut anyone who is only there to be informed. Replace status updates with pre-reads. End every call by saying the decision out loud.
Most meetings end without a decision because nobody owned the call
Walk into a room of seven smart people, talk for 50 minutes, and you will get seven smart opinions. That is not a bug, it is what discussion does. A decision is a different shape. A decision means one person, with the authority to choose, says "we are going with this," and the room accepts it. Without that single owner, every meeting is a feeling, not a decision.
The fix is small and uncomfortable. Before the meeting starts, write the decider's name on the agenda. Not the team, not the working group, one human. If you cannot name that person, you do not have a decision meeting. You have a brainstorm, which is fine, but call it that and move on.
Sharpen the question until it can be answered with a yes, no, or A-or-B
The single biggest predictor of whether a meeting decides anything is the shape of the question on the table. "Let's discuss pricing" never decides anything. "Should we ship the $19 plan as the default starting May 6?" decides in twelve minutes.
Three formats almost always work:
- Yes or no. "Do we approve the contract as drafted?"
- A or B. "Do we ship in May with two SKUs, or in June with three?"
- Rank these three. Used when you need a stack-ranked priority, not a binary.
If the question does not fit one of those shapes, the work to sharpen it has not been done yet. Send it back to the proposer. A single one-pager that frames the question as a yes-or-no is worth more than an hour of free-form discussion.
Invite only people who change the answer or execute it
Every additional attendee adds friction without adding signal. The right invite list for a decision meeting has three categories of people, and only three:
- The decider.
- People whose information or expertise can change the decider's answer.
- The single person who will own the action coming out of the meeting.
Everyone else gets the recap. This feels harsh, especially in cultures where presence is read as importance. Tell people directly: "I want your time back. I will send the decision and the reasoning." Most people are relieved.
A useful test from Amazon's two-pizza rule: if the room would not be fed by two pizzas, the room is too big to decide.
Replace status updates with a written pre-read
Status updates are the loudest, slowest, lowest-value part of most meetings. They are also the easiest to fix. The rule: if a fact can be read in 90 seconds, it must not be spoken in the meeting. Send it in a one-page pre-read 24 hours ahead, or in a Slack thread the morning of.
Then the meeting opens with five minutes of silent reading, and the rest is reaction, debate, and decision. This is the Bezos memo format, but you do not need to be Amazon to use it. A Notion doc with five short sections works fine.
Teams that adopt this almost always cut their meeting load by half within a quarter, because once status reporting moves to writing, half the meetings on the calendar lose their reason to exist.
Open the meeting by saying what kind of meeting it is
Half the wasted time in meetings comes from people not knowing whether they are brainstorming, deciding, or being informed. Say it in the first 30 seconds.
"This is a decision meeting. The question is whether we ship in May or June. I'm the decider. I'd like to hear from engineering and design, then I'll call it by 2:25."
Three sentences, and the room knows the rules. Watch how the energy of the conversation shifts when this is said out loud versus when it is left implicit. People stop performing. They start contributing the specific thing they are there to contribute.
Use a 25-minute default, not 60
Calendar tools default to 30 or 60 minutes because Microsoft Outlook did, in 1997. There is no cognitive reason for those numbers. A sharp question, a small room, and a written pre-read can almost always be resolved in 25 minutes.
The mechanism is not magic. Long meetings expand to fill the time because people feel obligated to keep talking. Short meetings force the room to focus on the question. If 25 minutes feels impossible, the question is not sharp enough yet, or the wrong people are in the room.
Reserve longer meetings for genuine working sessions: design crits, retros, customer interviews. Decisions are not working sessions.
Close every meeting with three lines, said out loud
This is the single highest-leverage habit you can install. Before anyone leaves the call, the decider says three sentences, in this order:
- What we decided. One sentence.
- Who owns the next step. One name, not a team.
- When it ships, or when we check in. A date.
The reason to say it out loud, not write it later, is that any disagreement surfaces immediately. Half the time someone in the room thought the decision was different. Better to find out now than three days later when the action item arrives in their inbox.
If you cannot name those three things, the meeting did not decide. Schedule a follow-up with a sharper question. That is honest. Pretending you decided when you did not is how teams end up doing the same meeting four times.
Make the decision discoverable after the meeting
A decision that lives in someone's head, or in a meeting transcript no one reads, will be re-litigated next month. The team will not remember why you chose option A. They will rebuild the case for option B from scratch.
Two patterns work:
- A team decision log. A single Notion page or doc with one line per decision: date, what was decided, who decided, why. Searchable and short. Not minutes, just the result.
- Inline in the source of truth. If the decision is about pricing, write it on the pricing doc. If it is about a feature, write it on the spec. Decisions belong where the work lives.
This is also where ambient AI earns its keep. A voice teammate in the room can write the three closing lines, the decider, and the rationale into the team's decision log without anyone leaving the conversation. (See what ambient AI actually means for the broader picture.)
The cultural shift, not just the tactics
Tactics get you 60% of the way. The other 40% is a cultural belief that meetings are expensive and deciding is a skill. Teams that decide well treat a wasted meeting like a wasted deploy: a small failure worth a five-minute retro. Teams that decide badly treat meetings like weather, something that happens to them.
You do not need permission to start. Pick your next recurring meeting. Add the decider's name to the agenda. Sharpen the question to a yes-or-no. Cut the invite list. Run it in 25 minutes. Close with the three lines. You will feel the difference inside a week.
Where relly fits
relly is a voice AI teammate that joins your meetings on Zoom, Google Meet, or Microsoft Teams. It listens to the conversation, captures the decision and owner without anyone typing, and writes the three closing lines into your team's decision log automatically. The room stays in flow. The decision becomes searchable the second the meeting ends.
If your team is trying to decide more and meet less, early access gets you in before public launch, with 50% off for your first 12 months.
Common questions
What makes a meeting actually decide something?
A meeting decides something when one person owns the call, the question on the table is sharp enough to answer with a yes, no, or pick-A-or-B, and the room agrees on a single next action with an owner and a date before anyone leaves. Without those three, you held a discussion, not a decision meeting.
How long should a decision meeting be?
Most decision meetings should be 25 minutes or less. Long meetings hide bad framing. If you need 60 minutes to decide one thing, the question is not sharp yet, and pre-reads or a written proposal will do more than extra meeting time.
Who should be in a decision meeting?
Invite only the decider, the people who can change the decider's mind, and one person who will execute the outcome. Anyone who is purely informed should get the recap instead. Larger rooms slow decisions because every voice creates an obligation to respond.
How do you stop a meeting from ending without a decision?
End every meeting with three lines spoken out loud: what we decided, who owns the next step, and when it ships. If you cannot say those three lines, schedule a follow-up with a sharper question instead of letting the room drift away believing something was settled.
Want a meeting that decides without a notetaker?
relly listens in your meeting, captures the decision and the owner, and writes it to your team's log while you keep talking. Early access is open through May 18, 2026, with 50% off for your first year.
Claim early access →