Meetings into Action: Facilitation & Follow‑Up Playbook

Welcome — Purpose and how to use this playbook

This playbook helps teams design meetings that consistently produce clear decisions, named owners, useful evidence, and reliable follow‑up. Use the sections below to pick a meeting type, run a predictable facilitation routine, capture outcomes in standard artifacts, and close the loop with a simple review cadence so learning accumulates in organizational memory.

Quick Meeting Design Matrix

Choose the meeting pattern that matches your primary outcome. Use the recommended duration and artifacts as starting points and adapt for your context.

Facilitator Script (timeboxed template)

Use this script as a scaffold. Tweak times and prompts for your meeting type.

Role Cards (short)

• Facilitator: Keeps timeboxes, enforces process, captures decisions and owner commitments.
• Timekeeper: Announces remaining time before and at timebox end—supports facilitator.
• Scribe / Recorder: Fills Decision Record, Action List, and uploads artifacts to shared space.
• Decision Owner: Responsible for executing the decision and reporting progress.
• Participants: Come prepared, ask clarifying questions, avoid raising new topics outside the agenda.

Decision Record (artifact template)

Capture these fields every time you make a decision.

Meeting Notes Template (turn outputs into backlog items or experiments)

1. Meeting title, date, attendees, facilitator, scribe.
2. Top outcome (one sentence).
3. Decision Records (one per decision) — include Decision ID and owner.
4. Action Items — for each: owner, due date, status, link to task in backlog/tool.
5. Experiments / Follow‑ups — hypothesis, measurement, owner, duration.
6. Parking lot items (explicit handoff to backlog or next agenda).
7. Quick learning note: one insight, one improvement for next meeting.

After the meeting, the scribe should convert actions and experiments into tracked backlog items (or create lightweight tickets) within 24 hours and tag them with the Decision ID where relevant.

Owner & Follow‑Up Checklist

Use this checklist to avoid lost actions.

• Pre‑meeting: confirm agenda, required evidence, and attendee preparedness.
• During meeting: name owner(s) in the Decision Record and confirm due dates.
• Immediately after: scribe posts Decision Record and action items to the shared workspace and assigns tickets.
• Within 48 hours: owner acknowledges assignment in the backlog/task system and adds a short plan.
• At the next sync: owner reports progress against the success measure; facilitator flags blocked items for escalation.

Daily / Weekly Review Cadence to Surface Learning

Simple rhythm to make meeting outputs visible and learning actionable:

• Daily (standup/tactical): Surface blockers and critical next steps. Owner when blocked should request help or escalate.
• Weekly (tactical review): Review open decisions and actions older than 7 days. Update Decision Records with progress notes.
• Monthly (learning review): Ask: Which decisions had expected outcomes? Which assumptions were wrong? Capture two short learning notes and assign an experiment if needed.
• Quarterly (course correction): Review clusters of decisions and outcomes; retire or codify recurring decisions into playbooks, policies, or checklists.

Lightweight Meeting Health Assessment

After a meeting, ask the group to score these quickly (scale 1–5) or use a quick poll:

• Clarity of purpose
• Evidence and preparation
• Decision or useful outcome
• Clear owners and next steps
• Time well used

If average score on any item is <3, capture one concrete improvement for the next meeting.

Common Mistakes and Quick Fixes

• Mistake: Meetings become status reports. Fix: Replace with a written update + short sync for exceptions.
• Mistake: Owners are vague. Fix: Always require owner + specific next action + date in the Decision Record.
• Mistake: Too many agenda items. Fix: Prioritize the most important outcome and save others for a follow‑up meeting or async thread.
• Mistake: No evidence used. Fix: Require the presenter to submit 1–3 supporting artifacts before the meeting.

Adaptations & Examples

Small teams: run decision meetings as 30-minute sessions with 10/10/5 timeboxes (context/questions/decision). Service businesses: add a 5‑minute customer impact check. Ops shifts: attach a short safety/quality check to each agenda.

Next Steps — Make this playbook yours

Start small: pick one recurring meeting, adopt the Decision Record and Owner Checklist for four iterations, and run the Lightweight Meeting Health Assessment after each meeting. After a month, review learning notes and iterate on the script and artifacts.