Team Facilitation
Input: $ARGUMENTS
Step 1: Define the Session Goal
Clarify what this session must produce.
SESSION GOAL: [What specific outcome must exist when the session ends?]
GOAL TYPE: [DIVERGENT (generate ideas) / CONVERGENT (narrow options) / ALIGNMENT (build shared understanding) / DECISION (choose a path)]
SUCCESS LOOKS LIKE: [How will you know the session worked?]Step 2: Choose Facilitation Method
Select the method that fits the goal and group size.
| Method | Best for | Group size | Energy level |
|---|---|---|---|
| Brainstorm | Generating many ideas fast | 4-12 | High |
| Fishbowl | Surfacing perspectives on charged topics | 8-30 | Medium |
| World Cafe | Cross-pollinating ideas across subgroups | 12-50 | Medium-High |
| Dot Voting | Prioritizing from a long list | 4-30 | Low |
| 1-2-4-All | Getting input from everyone, including quiet voices | 4-40 | Medium |
| Six Thinking Hats | Examining a topic from multiple angles | 4-12 | Medium |
| Lightning Decision Jam | Moving from problems to solutions quickly | 4-8 | High |
| Open Space | Self-organizing around emergent topics | 20-100+ | Variable |
CHOSEN METHOD: [method]
RATIONALE: [why this fits the goal and group]
BACKUP METHOD: [if the primary method stalls]Step 3: Design the Agenda with Time Boxes
Build a structured timeline. Every block gets a hard time limit.
AGENDA:
1. [MM min] Opening — State purpose, set ground rules
2. [MM min] Context setting — Share necessary background
3. [MM min] Core activity — [the chosen method]
4. [MM min] Synthesis — Capture themes and patterns
5. [MM min] Decision/Next steps — Lock in outputs
6. [MM min] Close — Confirm actions, get feedback
TOTAL TIME: [HH:MM]
BUFFER: [built-in slack for overruns — recommend 10-15%]Step 4: Assign Roles
Every effective session has explicit roles.
ROLES:
- FACILITATOR: [guides process, stays neutral on content]
- TIMEKEEPER: [enforces time boxes, gives warnings]
- NOTE-TAKER: [captures decisions, actions, parking lot items]
- PROCESS OBSERVER: [optional — watches dynamics, gives feedback at end]Note: The facilitator should NOT also be the decision-maker. If the leader must decide, someone else facilitates.
Step 5: Plan for Dominant and Quiet Participants
Anticipate and design around group dynamics.
FOR DOMINANT VOICES:
- Use round-robin or structured turns
- Implement "one talk, all talk" rule
- Use silent writing before discussion
- Assign them specific roles (timekeeper, note-taker)
FOR QUIET PARTICIPANTS:
- Start with individual reflection (writing/sticky notes)
- Use pair discussions before full group
- Invite (don't demand) contributions: "What would you add?"
- Use anonymous input methods (digital polls, written cards)
KNOWN DYNAMICS TO MANAGE:
- [any specific interpersonal or power dynamics to plan for]Step 6: Create the Output Template
Define the deliverable before the session starts.
SESSION OUTPUT TEMPLATE:
Session: [name]
Date: [date]
Participants: [list]
DECISIONS MADE:
1. [decision] — Owner: [name] — By: [date]
ACTIONS:
1. [action] — Owner: [name] — By: [date]
PARKING LOT (topics deferred):
1. [topic] — Follow-up: [how/when]
OPEN QUESTIONS:
1. [question]Integration
Use with:
/mtgd-> Design the meeting structure around the facilitation/csb-> When the session goal is reaching group agreement/dshb-> Track outcomes and follow-through from sessions