facilitation-design

---
name: facilitation-design
description: Apply facilitation-design whenever the user needs to plan a meeting, workshop, retrospective, or any group session aimed at a specific outcome. Triggers on phrases like \"design a workshop\", \"how do I run this meeting?\", \"facilitate a retrospective\", \"structure a brainstorm\", \"we need alignment\", \"how do I get the group to decide?\", \"plan an offsite session\". Use proactively when a user describes a group decision-making challenge, alignment gap, or collaborative work session that lacks structure.
license: MIT
---

# Facilitation Design

**Core principle**: Good facilitation structures participation so the best thinking surfaces, regardless of who holds it. Bad meetings let the loudest voice win.

---

## When to Use This Skill

- A group needs to make a decision, generate ideas, or align on direction
- A meeting keeps happening but produces no outcomes
- Power dynamics or personality differences suppress useful input
- A workshop or offsite needs a structured agenda with clear deliverables
- A retrospective needs to surface honest feedback

---

## Core Methodology

### Step 1: Define the Session Outcome

State what must be true at the end that isn't true now. Be specific:

- **Bad**: "Align on the roadmap" (vague — how would you know?)
- **Good**: "Produce a ranked list of Q3 priorities with owner assignments that all leads have explicitly approved"

If the outcome can't be stated concretely, the session isn't ready. Clarify before designing.

Classify session type:
- **Divergent** — generate options (output: a long list)
- **Convergent** — narrow, decide, commit (output: a decision or ranked list)
- **Alignment** — share context, build shared understanding (output: documented mental model)
- **Retrospective** — reflect, extract lessons (output: action items)

### Step 2: Analyze the Participants

- **Expertise distribution** — who knows what? Where are the gaps?
- **Power dynamics** — formal authority? informal influence? who dominates?
- **Stakes** — who cares most? who might disengage?
- **Communication styles** — introvert/extrovert mix, remote vs. in-person

This determines participation architecture in Step 3. High power asymmetry → more anonymous/written input. Introvert-heavy → individual think time before discussion.

If stakeholder-power-mapping has run, use its output directly.

### Step 3: Design the Activity Sequence

Follow the **diverge → cluster → converge** arc.

1. **Opening** (5-10 min) — state outcome, explain process, set ground rules.

2. **Diverge** (15-30 min) — generate input broadly. Anti-anchoring techniques:
   - **Silent writing first** — everyone writes individually before discussion
   - **Round-robin** — each person shares one idea in turn
   - **1-2-4-All** — alone, pair, quad, full group

3. **Cluster** (10-15 min) — affinity mapping: group related ideas, name groups, identify gaps.

4. **Converge** (15-30 min) — narrow to decisions:
   - **Dot voting** — each person gets N votes
   - **Effort/impact matrix** — surface quick wins and strategic bets
   - **Gradients of agreement** — 5-point scale "fully support" → "block"

5. **Close** (5-10 min) — what was decided, who owns what, next checkpoint. Confirm explicitly — don't take silence as agreement.

**Timeboxing rule**: Allocate by outcome value, not item count. Convergence gets ≥30% of total time.

### Step 4: Choose the Decision Protocol

Decide before, announce at the start:

- **Consensus** — everyone agrees. Small groups (<7), high trust, low time pressure.
- **Consent** — no principled objection. Faster than consensus; good for operational decisions.
- **Majority vote** — quick but alienates minorities. Low-stakes or reversible decisions.
- **Authority with input** — one person decides after hearing the group. Best when accountability is clear and speed matters. Name the decider.

Mismatched decision-protocol expectations cause more meeting dysfunction than any other factor.

### Step 5: Engineer Psychological Safety

- **Anonymous input** — written submissions, polls, digital tools for sensitive topics
- **Structured turns** — prevent "popcorn" discussion where only the confident speak
- **Devil's advocate** — assigned, rotated role
- **Pre-work** — distribute context beforehand so the most-prepared doesn't dominate
- **Explicit permission to disagree** — facilitator models: "What's the strongest argument against what we just decided?"

---

## Output Format

### 🎯 Session Goal
- **Outcome**: [what must be true at the end]
- **Session type**: Divergent / Convergent / Alignment / Retrospective
- **Duration**: [total time]
- **Decision protocol**: [type — name decider if applicable]

### 👥 Participant Profile

| Role | Name/Count | Expertise | Power Level | Key Concern |
|------|-----------|-----------|-------------|-------------|
| [role] | [who] | [what they know] | H/M/L | [what they care about] |

### 📋 Agenda

| Time | Phase | Activity | Method | Output |
|------|-------|----------|--------|--------|
| 0:00-0:10 | Opening | State outcome, ground rules | Facilitator-led | Shared purpose |
| 0:10-0:30 | Diverge | [activity] | [silent write / round-robin / 1-2-4-All] | [list] |
| 0:30-0:45 | Cluster | [activity] | [affinity mapping] | [themes] |
| 0:45-1:10 | Converge | [activity] | [dot vote / matrix / gradients] | [decision] |
| 1:10-1:20 | Close | Confirm decisions, assign owners | Facilitator-led | [actions + owners + dates] |

### 🧠 Facilitation Notes
- **Opening prompt**: "[exact words]"
- **Transition cues**: "[diverge → cluster → converge]"
- **If energy drops**: [change format, break, switch to pairs]
- **If conflict arises**: [name disagreement, use decision protocol]
- **If time runs short**: [what to cut, what to protect]

### ✅ Follow-Up
- **Decisions made**: [list]
- **Action items**: [owner + action + deadline]
- **Next checkpoint**: [when and how]

---

## Thinking Triggers

- *"If I removed this agenda item, would the session still achieve its outcome?"*
- *"Who has relevant knowledge but won't speak without structure?"*
- *"Am I giving enough time to convergence?"*
- *"What's the decision protocol — and does everyone know it?"*
- *"If the loudest person is wrong, will this design surface that?"*

---

## Common Traps

**No clear outcome**: "Let's discuss X" isn't a goal. Can't state what's different after? Cancel the meeting.

**Skipping divergence**: Jumping to convergence means choosing among whatever the first speaker suggested. Generate before evaluating.

**Consensus theater**: Group appears to agree but individuals privately disagree. Use explicit commitment checks ("thumbs up / sideways / down"), not "any objections? No? Great."

**Facilitator as participant**: Running the process *and* advocating a position. If the facilitator has a stake, assign a separate facilitator or declare upfront.

**Ignoring remote participants**: In hybrid sessions, remote loses to in-room dynamics. Equalize via digital-first input (chat, shared docs) even when some are co-located.