How to run a meeting that ends in a decision

For a decision meeting, define the choice, bring the evidence and leave with a recorded next step. Other meetings may legitimately exist for learning, support or connection.

Skip illustration and read article

Eight people in a one-hour meeting use eight person-hours. That arithmetic alone does not tell you whether the meeting was worthwhile: a useful training session may produce understanding rather than a decision.

This guide focuses on decision meetings. Use the worked agenda to make one choice clear, while preserving room for evidence that should change the plan.

The short answer

Match the meeting to its purpose, then record what happens next.

For a decision meeting, state the decision in the invitation, include the people and evidence needed, and identify who has authority to decide. End with the choice or unresolved question, action owner and follow-up date. Learning, support and relationship meetings need different outcomes. Consider a written update when discussion adds little value.

The method

Six steps, in order.

A decision meeting needs a clear question and a fair way to hear the information that can change it.

State the choice and desired result

Write the question in the invitation, such as whether to run a small pilot or launch more widely. If the purpose is support or learning, name that purpose instead.

Include the necessary knowledge and authority

Invite people whose input or participation is needed, not only the final decision-maker. Offer a way to contribute in advance and share the outcome with affected people.

Make context accessible

Share the options, evidence and uncertainties early enough to review. If necessary, reserve reading time in the meeting. Check that people can access the material and participate.

Confirm who decides and how

Name the decision owner and constraints at the start. Clarify whether the group is advising, seeking agreement or making a collective decision.

Separate drift from relevant new evidence

Park a different issue with an owner. If new information changes the risk or choice in front of you, examine it or pause the decision rather than dismissing it as off topic.

Record the outcome and next check

Write the decision or unresolved question, rationale, action owner and date. If the purpose has been met, finish. If evidence is missing, assign the follow-up instead of forcing certainty.

In practice

A worked 25-minute decision agenda.

Original example: Ana needs to choose between a five-customer pilot and a wider release. The hypothetical constraint is that support capacity has not yet been checked.

Use five minutes to confirm the decision and known constraints, ten to compare options, five to examine unanswered questions and five to record the result. These add to 25 minutes; they are planning allowances, not a proven ideal length.

A possible decision note: "Run the five-customer pilot if support confirms coverage by Thursday. Ana owns the release decision. Sam checks coverage. Review the pilot before deciding on wider release." This records a condition and keeps the wider launch undecided.

Check your own agenda: could an attendee state the choice, who owns it and what evidence would change it? Could someone absent understand the next action from the note?

In practice

Invite participation without putting someone on the spot.

Ask for written input before the meeting, pause for thinking and invite contributions without requiring an immediate public answer. A quiet attendee may need more context, time or another channel.

When one person dominates, restate the question and make room for other views. When a concern arrives later, assess its substance. New information can matter even if it did not arrive at your preferred time.

In practice

Review the calendar by purpose.

Ask what each recurring meeting enables and whether another format would serve that need. Test a written update for a routine status meeting where discussion is unnecessary; retain meetings that provide useful support or collaboration.

We build Cadence. Its courses on meetings and using your calendar offer practice around these decisions. They do not establish that shorter meetings or fewer meetings are always better.

Put it into practice

Start it today, one lesson at a time.

If you want to keep going, Cadence turns what brought you here into a course with practice and saved progress. Learn at your own pace. Cadence is our app.

Download on the App Store Get it on Google Play

Want new features first?

Communication course Running effective meetings Turn meetings into decisions, owners, and next steps instead of another hour of context sharing. See what the course covers See how Cadence works

Questions

Common questions.

Should every meeting end in a decision?

No. Learning, support and connection can be valid purposes. A decision meeting should produce a decision or an explicit account of what is missing and who will follow up.

Who should attend a decision meeting?

Include the necessary decision authority, knowledge and affected perspectives. Let others contribute beforehand or read the outcome where appropriate.

How long should a meeting be?

Allow enough time for its purpose and necessary participation. Finish when that purpose is met, and pause a decision when important evidence is missing. There is no universal ideal length.

What should the meeting notes include?

For a decision meeting, record the choice, rationale, assumptions, action owner and date. Distinguish a proposal from a confirmed decision.

Continue in Cadence

Turn what brought you here into a course you can keep building.

Use the article now. If you want to go further, Cadence can turn the problem or curiosity behind it into a structured course. Cadence is our app.

Download on the App Store Get it on Google Play

Want new features first?