Hold a meeting when people need live interaction to decide, resolve, create, coordinate, or learn together. State the intended outcomes, invite only needed participants, provide context in advance, facilitate the discussion, and record decisions and actions. Use an asynchronous update when information can be understood without a shared conversation.
Who this is for: Managers and team leads responsible for recurring or one-time meetings involving decisions, coordination, problem solving, or learning.
- Choose a meeting only when synchronous interaction serves a defined outcome better than an update or document.
- Design the agenda around decisions and discussion, with preparation, roles, and decision authority made clear.
- Facilitate contribution and close with decisions, owners, open questions, and communication to affected people.
Decide whether to meet
Begin with the outcome: a decision, resolved dependency, generated options, shared interpretation, practiced skill, or relationship-sensitive discussion. If the purpose is only to distribute information, use a readable update and offer a route for questions. Habit is not enough reason to take everyone's shared time.
Invite people whose authority, knowledge, implementation responsibility, or affected perspective is needed. Others can receive the record. Be careful not to exclude less senior experts while filling the room with observers. For recurring meetings, periodically check which outcomes still require the group and remove agenda items that have become routine reporting.
Prepare for the intended outcome
Write agenda items as actions or questions, not topic labels. 'Decide which migration risk blocks launch' tells participants how to prepare; 'migration update' does not. Name the decision owner and provide concise context with enough lead time for meaningful review. Avoid using a dense pre-read as a test of personal dedication.
Choose a facilitation approach that fits the task. Independent idea generation can prevent early anchoring, a structured round can surface distributed knowledge, and open debate can test a developed proposal. None guarantees a good result. The facilitator still needs to clarify claims, manage time, and address behavior that prevents contribution.
Guide the discussion
Open by stating the outcome, constraints, available time, roles, and decision method. Keep the group on the question while allowing relevant new facts to reshape it. Separate information gaps from disagreements about values or tradeoffs. Parking a consequential issue merely because it is uncomfortable can produce a fast but weak decision.
Watch who speaks, who is interrupted, and whose expertise is being used. Invite relevant voices directly without forcing personal disclosure. Summarize areas of agreement and disagreement as the conversation develops. If the group lacks authority or essential evidence, decide the next step rather than pretending the meeting reached a conclusion.
Turn discussion into follow-through
Before closing, state each decision, action, owner, expected timing, unresolved question, and escalation. Ask the group to correct the summary. A note taker should capture reasoning that later readers need, not a transcript of every comment. Communicate outcomes to affected people who were not present.
Review actions at the relevant future point and examine meeting usefulness periodically. Evidence can include whether intended decisions were made, required participants were prepared, actions closed, and recurring items still need synchronous time. Calibrate format and cadence from the team's work rather than adopting a universal meeting rule.
Redesign a weekly coordination meeting
A cross-functional meeting consists of long status recitals, while dependency decisions are rushed at the end.
- Move standard updates into a shared written format and ask participants to flag only changes that require group attention.
- Rewrite the live agenda around dependency decisions, naming each owner, required evidence, and affected functions.
- Facilitate the decisions before optional discussion, summarize disagreement, and assign missing evidence rather than forcing closure.
- Publish decisions and actions, then review whether the new format resolves coordination needs using the team's experience.
Outcome-based meeting plan
Prepare this plan for any meeting whose cost or consequence warrants deliberate design.
- Purpose: intended outcome, reason synchronous interaction is needed, and what happens without the meeting.
- Participants and roles: decision owner, facilitator, knowledge holders, implementers, affected perspectives, and note owner.
- Agenda: questions or decisions, preparation, evidence, method, constraints, and time allocation.
- Closeout: decisions, rationale, dissent, actions, owners, open questions, communication, and review point.
Common mistakes
- Holding a recurring meeting for information that participants could understand from a concise written update.
- Naming agenda topics without stating which question, decision, or preparation is required.
- Ending after energetic discussion without confirming decisions, owners, and unresolved evidence.
Try one
A meeting needs a decision, but the authorized owner cannot attend. What should the facilitator do?
A strong answer checks whether the owner can delegate authority or provide explicit decision criteria. If not, the group can clarify options, evidence, risks, and a recommendation, but should not mislabel that work as a final decision. The facilitator records what remains open, names the route and timing for approval, and communicates the result afterward to participants and affected people.
Sources
- Atlassian working agreements playA facilitated method for agreeing how a team will communicate, decide, and work together.
- Atlassian DACI decision playA practical method for naming the driver, approver, contributors, and informed people for a decision.