Overview
Meetings usually run long not because there are too many people, but because the purpose is unclear and there are no ground rules.This skill helps with the facilitation design: before the meeting, it pins down the purpose, agenda, and deliverables; during the meeting, it manages time and speaking turns; after the meeting, it ensures decisions and owners remain. It reduces time spent gathering and increases lasting conclusions.
Trigger Keywords
meeting, meeting facilitation, agenda, facilitation, off-track meeting, decision-making meeting, meeting minutes, meeting prep, running a meeting, meeting rules, follow-up actions
Workflow
Step 1: Define the meeting’s purpose and deliverables
Before scheduling the meeting, answer in one line. If you can’t answer, it’s something to finish with a message instead of a meeting.
- What should remain when this meeting ends? (decision / alignment / ideas / sharing)
- Classify the meeting type:
| Type | Purpose | What remains when it ends |
|---|---|---|
| Decision-making | Decide among options | Decision + owner + deadline |
| Alignment/Sharing | Get on the same page | Shared understanding and next steps |
| Divergence/Ideas | Expand possibilities | List of candidates + criteria for the next judgment |
| Problem solving | Unblock what’s stuck | Cause + solution + owner |
Step 2: Design the agenda (time boxes)
For each agenda item, purpose, time, and deliverablemust be attached. Vague "discuss ○○" is not allowed.
- Each agenda item: title / purpose (decision, sharing, divergence) / allotted time / who presents
- Place heavy decision items early (when energy is high)
- Circulate pre-read materials in advance to eliminate "reading time" in the meeting
- If there are more than 5 agenda items, split the meeting or move some to async
Step 3: Ground rules (so it doesn’t go off track)
Agreeing on rules in the first 30 seconds of the meeting makes it easier to keep it on track.
- Assign a timekeeper and a note-taker: if the facilitator does both, they’ll miss both
- Parking Lot: off-topic discussions are written on the board for later. "I’ll put that in the parking lot"
- Speaking balance: guide talkative people to summarize, and directly call on quiet people to hear their opinions
- Conclusion signal: for each agenda item, nail it down with "So what we decided is ○○, right?" and move on
Step 4: Drawing Out Decisions
To end a meeting that isn't producing a decision, decide the decision method in advance.
- Agreeing on the decision method: consensus / majority vote / single decision-maker (simplified versions of RAPID, DACI, etc.)
- Narrowing the options: Instead of endless debate, compress to 2–3 proposals and compare
- When you can't decide: Determine what more is needed to decide (data, approval) and who will do what by when, then close
- Write the decision on the spot as a sentence and confirm everyone saw the same thing
Step 5: Meeting minutes + follow-up actions
The point of the record is not transcribing the meeting content but decisions and to-dos.
- 3-line meeting minutes: decisions / action items (owner, deadline) / on hold, next agenda items
- Share right after the meeting (same day) — as time passes, the agreement blurs
- Action items should include owner, deadline, and completion criteria. Not "review ○○" but "A/B comparison proposal by Friday for ○○"
Usage examples
Example 1: "Our weekly meeting tomorrow keeps running over an hour—how do we shorten it?" → Redefine the purpose → time-boxed agenda per item → timekeeper and parking lot rules → 3-line meeting minutes template
Example 2: "I need to run a decision-making meeting to prioritize new features" → Agree on the decision method in advance → compress to 2–3 candidate proposals → comparison criteria table → phrase the decision + owner and deadline
Example 3: "The meeting keeps drifting off topic and we never reach a conclusion" → Parking lot rule + conclusion signal phrases → split or make asynchronous when more than 5 agenda items → facilitation script
Deliverables
- One-line definition of the meeting's purpose, type, and deliverables
- Time-boxed agenda (agenda items, purpose, time, presenter)
- Set of facilitation rules (timekeeper, parking lot, conclusion signals)
- Decision method and comparison proposals
- 3-line meeting minutes + action items (owner, deadline) template
Precautions
- Not every gathering needs to be a meeting. Sharing and reporting are often faster as asynchronous messages.
- The facilitator is a flow manager, not an opinion owner. Pushing your own argument breaks the balance.
- If you don't phrase the decision, everyone remembers it differently even after the meeting ends.
Related skills
- moai-coworker:collab-report-speak: Lead with the conclusion in meetings when presenting or reporting
- moai-coworker:collab-negotiation: Align with and persuade key people before the meeting
- moai-coworker:collab-conflict: Handle conflict and speaking monopolization during the meeting
- moai-officer:doc-docx: Turn meeting minutes into a formal document
Post-processing chain (written deliverables such as meeting minutes and facilitation scripts)
After writing sentence-based deliverables such as meeting minutes and facilitation scripts, finish with the chain below.
- moai-coworker:ai-slop-reviewer: Review and revise AI-sounding expressions, exaggeration, and clichés (required)
- moai-writer:korean-humanize: Korean naturalness adjustment — after slop review (required)
When not to use this skill
- Writing meeting minutes and planning documents: Written outputs use
moai-coworker. This skill focuses on process design. - Personal schedule and to-do management: My work plan uses
moai-coworker. - Designing workshops and training programs: Long-duration facilitation curricula require separate design.
Source
Referenced general meeting facilitation frameworks (agenda time boxes, parking lot, decision-making methods) + user vault notes. Wording and examples are independently composed based on South Korea as of 2026.