Playbook

Meetings Playbook: Agenda Patterns & Decision Records

A practical playbook with a meetings types matrix, plain-language pre-read checklist, adaptable agenda patterns (status, planning, decision, retrospective), facilitator prompts and scripts, a clear decision record template, and a follow-up tracker to close actions and preserve organizational memory.

Make meetings predictable, inclusive, and outcome-focused

Good meetings return time and clarity. This playbook helps teams turn recurring gatherings into short, decision-oriented moments that leave everyone with clear ownership and next steps. Use the patterns and templates below as starting points — adapt timings, names, and roles to your team.

What to decide before you schedule

  • Meeting Type: choose a pattern that matches the primary purpose (status, planning, decision, or retrospective).
  • Intended Outcome: write the one-sentence outcome on the invite (e.g., “Decide FY24 roadmap priorities” or “Agree on release scope for v1.3”).
  • Required Attendees: list only people needed to achieve the outcome; optional attendees can review the decision record later.
  • Preparation: attach a pre-read that contains the facts, options, and a recommended proposal.

Meetings types matrix (quick guide)

  • Status: keep teams aligned, surface blockers, and escalate only what needs cross-team coordination. Not for long-form problem-solving.
  • Planning: set short- to medium-term plans, allocate effort, and sequence work where trade-offs matter.
  • Decision: deliberate among options and record the decision and rationale. Invite decision-owners and key stakeholders only.
  • Retrospective: reflect on recent work to identify experiments and improvements; focus on small, testable changes.

Pre-read checklist (strip to essentials)

  • Purpose and intended outcome (one sentence).
  • Relevant data or metrics summarized (2–4 bullets).
  • Options or proposals (brief) with trade-offs noted.
  • Recommendations (if any) and the decision you’re asking for.
  • List of required attendees and their role in the decision.
  • Time estimate for discussion and decision (so people can prepare).

Starter agenda patterns (adapt timing to team size)

Status Pattern (short, regular alignment)

  1. Welcome & outcome reminder (2–3 min)
  2. Round for high-impact updates / blockers (15–25 min total, timebox per person)
  3. Escalations & coordination (5–10 min)
  4. Parking lot review & action assignment (3–5 min)

Planning Pattern (scope & commitments)

  1. State the planning outcome and constraints (5 min)
  2. Review data and assumptions (10–20 min)
  3. Discuss options and capacity (20–30 min)
  4. Agree commitments and owners (10–15 min)
  5. Record decisions and next steps (5 min)

Decision Pattern (focus on choosing)

  1. Read the decision statement and desired outcome (3 min)
  2. Clarifying questions about facts only (5–10 min)
  3. Discuss options and trade-offs (20–30 min)
  4. Call the decision using the chosen protocol (consent, majority, or designated owner) and record it (5–10 min)
  5. Assign immediate next actions and owners (5 min)

Retrospective Pattern (learning + experiments)

  1. Set the stage: safety and what we’ll focus on (5 min)
  2. Collect observations (data, feelings, examples) (10–20 min)
  3. Identify patterns and root causes (10–20 min)
  4. Agree 1–3 experiments and owners (10 min)
  5. Schedule short follow-up & measure for learning (5 min)

Core meeting roles & short scripts

  • Facilitator (designated): “We’ll aim to finish in [time], outcome is [sentence]. I’ll keep us on topic and call timeboxes.”
  • Timekeeper: gently signals remaining time and enforces timeboxes; suggests parking lot when needed.
  • Note-taker / Scribe: records decisions, owners, and action items in the Decision Record template.
  • Decision Owner (when relevant): responsible for implementation and reporting progress; may escalate constraints as needed.

Facilitator prompts (practical phrases)

  • Clarify scope: “To be clear, what decision or outcome are we being asked for today?”
  • Focus on evidence: “What facts or data should change our view?”
  • Surface disagreement: “Who sees it differently and why?”
  • Check understanding: “Can someone summarize the proposal and its trade-offs in one sentence?”
  • Move to decision: “Based on what we heard, do we have consent to move forward with X?”

Decision record template

Copy this into meeting notes or your knowledge base for every substantive decision.

Decision Title: [short descriptive title]

Date: [YYYY-MM-DD] Recorded by: [name]

Context / Problem: 1–2 sentences describing why the decision matters.

Outcome sought: The explicit success criteria or what this decision enables.

Options considered: Bulleted list of the meaningful alternatives and key trade-offs.

Decision: The chosen option in plain language.

Rationale: Short reasons, data points, risks acknowledged, and key assumptions.

Owners & stakeholders: Owner(s) for execution, and who must be informed.

Key actions: A short list of next steps with owners and due dates.

Review date / checkpoint: When the owner will report back and what will be measured.

Follow-up tracker (use daily/weekly huddles to close actions)

Keep a simple running list of actions that teams review in a short follow-up huddle. This prevents decisions from evaporating.

Action Owner Due Status Notes
[Short action] [Name] [YYYY-MM-DD] [Not started / In progress / Done] [Progress or blockers]

Decision protocols — when to use which

  • Consent (advice and objections): use when speed and alignment matter; allow objections that are concrete and resolvable.
  • Majority vote: use for reversible, low-risk choices or where representation is formalized.
  • Designated owner: use when responsibility is clear and the owner is accountable for outcomes.

Common pitfalls and mitigations

  • Meetings that are status updates: move information that doesn’t require discussion into written updates and reserve meeting time for discussion or decision.
  • Loudest voices dominate: invite quieter perspectives, use round-robin prompts, or collect feedback in advance via the pre-read.
  • No follow-through: always record decisions and actions, assign owners and due dates, and review in a short follow-up huddle.

How to adapt this playbook

Treat these templates as starting points. Shorter teams may compress timelines, cross-functional groups may require a stronger pre-read, and regulated environments should capture additional compliance details in the decision record.

If you want this playbook to do more: convert the Decision Record and Follow-up tracker into a simple interactive form so decisions and actions are saved, searchable, and reportable in your organizational memory.

Discuss Ask the Librarian

Discussion

Comments and conversation will live here.