facilitation-patterns

$npx mdskill add lyndonkl/claude/facilitation-patterns

Design productive group sessions with structured facilitation patterns.

  • Helps run standups, workshops, design sprints, and team decision meetings.
  • Depends on user input about session type, goals, and participant count.
  • Recommends specific formats, agendas, and decision methods based on context.
  • Delivers clear step-by-step plans with time allocations and action items.

SKILL.md

.github/skills/facilitation-patternsView on GitHub ↗
---
name: facilitation-patterns
description: Provides structured formats and techniques for running productive group sessions, from standups to multi-day workshops. Covers format selection, agenda design, participation management, decision methods, and handling difficult dynamics. Use when running meetings, workshops, brainstorms, design sprints, retrospectives, or team decision-making sessions, or when user mentions facilitation, workshop design, meeting patterns, session planning, or effective collaboration.
---
# Facilitation Patterns

## Table of Contents
- [Workflow](#workflow)
- [Common Patterns](#common-patterns)
- [Guardrails](#guardrails)
- [Quick Reference](#quick-reference)

## Example

**Scenario**: Product team needs to prioritize features for Q2 (8 people, 90 minutes).

**Pattern**: Effort-Impact Workshop (diverge, assess, converge)

**Agenda**:
1. **Frame** (10 min): Present context, Q2 goals, constraints
2. **Diverge** (20 min): Silent brainstorm on sticky notes
3. **Cluster** (15 min): Group similar ideas, clarify duplicates
4. **Assess** (25 min): Plot on effort-impact 2x2 matrix (in pairs, then discuss)
5. **Converge** (15 min): Dot voting on quick wins
6. **Decide** (10 min): Top 5 by votes, facilitator makes final call with input
7. **Close** (5 min): Summarize decisions, next steps

## Workflow

Copy this checklist and track your progress:

```
Facilitation Planning Progress:
- [ ] Step 1: Define session objectives
- [ ] Step 2: Select facilitation pattern
- [ ] Step 3: Design agenda
- [ ] Step 4: Prepare materials and logistics
- [ ] Step 5: Facilitate the session
- [ ] Step 6: Close and follow up
```

**Step 1: Define session objectives**

What outcome do you need? (Decision, ideas, alignment, learning, relationship-building). Who attends? How much time? See [resources/template.md](resources/template.md#session-design-template).

**Step 2: Select facilitation pattern**

Based on objective and group size, choose pattern (Brainstorm, Decision Workshop, Alignment Session, Retro, Design Sprint). See [Common Patterns](#common-patterns) and [resources/methodology.md](resources/methodology.md#1-pattern-selection-guide).

**Step 3: Design agenda**

Create time-boxed agenda with activities, transitions, breaks. Follow diverge-converge flow. See [resources/template.md](resources/template.md#agenda-design-template) and [resources/methodology.md](resources/methodology.md#2-agenda-design-principles).

**Step 4: Prepare materials and logistics**

Set up space (physical or virtual), prepare slides/boards, send pre-work if needed, test tech. See [resources/template.md](resources/template.md#logistics-checklist).

**Step 5: Facilitate the session**

Run agenda, manage time, ensure participation, handle dynamics, track outputs. See [resources/methodology.md](resources/methodology.md#3-facilitation-techniques) and [resources/methodology.md](resources/methodology.md#4-handling-difficult-dynamics).

**Step 6: Close and follow up**

Summarize outcomes, clarify next steps and owners, gather feedback, share notes. See [resources/template.md](resources/template.md#closing-and-followup-template).

Validate using [resources/evaluators/rubric_facilitation_patterns.json](resources/evaluators/rubric_facilitation_patterns.json). **Minimum standard**: Average score ≥ 3.5.

## Common Patterns

**Pattern 1: Divergent Brainstorm (Generate Ideas)**
- **Goal**: Maximum idea generation, creative exploration
- **Format**: Silent individual brainstorm → share → cluster → refine
- **Techniques**: Crazy 8s, SCAMPER, "Yes, and...", defer judgment
- **Time**: 30-60 min for 5-10 people
- **Output**: 30-100 ideas, clustered by theme
- **When**: Need creative options, early in project, no single right answer

**Pattern 2: Convergent Decision Workshop (Choose Direction)**
- **Goal**: Narrow options, make decision with group input
- **Format**: Present options → assess criteria → vote/rank → decide
- **Techniques**: 2×2 matrix (effort-impact), dot voting, affinity grouping, forced ranking
- **Time**: 60-90 min for decision, 2-3 hours for complex
- **Output**: Prioritized list or single decision with rationale
- **When**: Multiple options exist, need buy-in, criteria clear

**Pattern 3: Alignment Session (Build Shared Understanding)**
- **Goal**: Get everyone on same page (vision, strategy, plan)
- **Format**: Present → Q&A → small group discussion → report back → synthesize
- **Techniques**: Fishbowl, gallery walk, 1-2-4-All, consensus check
- **Time**: 90-120 min for alignment, half-day for strategy
- **Output**: Shared mental model, documented assumptions, commitments
- **When**: Starting project, misalignment detected, new team formation

**Pattern 4: Retrospective (Reflect and Improve)**
- **Goal**: Learn from experience, identify improvements
- **Format**: Set context → gather data → generate insights → decide actions → close
- **Techniques**: Start-Stop-Continue, Mad-Sad-Glad, Timeline, Sailboat, 4Ls (Liked, Learned, Lacked, Longed for)
- **Time**: 45-90 min for sprint retro, 2-3 hours for project postmortem
- **Output**: 2-5 actionable improvements with owners
- **When**: End of sprint/project, recurring team practice, after incident

**Pattern 5: Design Sprint (Prototype and Test)**
- **Goal**: Rapidly prototype and validate concept
- **Format**: 5 days: Understand → Diverge → Decide → Prototype → Test
- **Techniques**: Sketching, storyboarding, Crazy 8s, Heat Map voting, user testing
- **Time**: 5 full days (can compress to 2-3 days)
- **Output**: Validated prototype, user feedback, go/no-go decision
- **When**: Big design decision, high uncertainty, time to test before committing

**Pattern 6: Asynchronous Collaboration (Remote/Distributed)**
- **Goal**: Collaborate across time zones, allow reflection time
- **Format**: Post prompt → async responses (24-48h) → sync synthesis session → document
- **Techniques**: Shared docs, threaded discussions, Loom videos, async voting (Polly, Simple Poll)
- **Time**: 2-5 days total (30-60 min sync session)
- **Output**: Documented decisions, rationale, action items
- **When**: Global team, deep thinking needed, no urgency for immediate decision

## Guardrails

1. **Objectives before format**: Start with "what outcome do we need?" not "let's do a brainstorm." If the objective is unclear, the session will drift.

2. **Time-box activities**: Parkinson's Law means work expands to fill time. Set strict timers, end activities even if incomplete. 25 minutes of focused work beats open-ended discussion.

3. **Separate divergence from convergence**: Defer judgment during brainstorming, because critiquing ideas early kills creativity. Generate first, evaluate second.

4. **Ensure psychological safety**: Set ground rules (no interrupting, critique ideas not people). Address power dynamics (boss speaks last, use anonymous input). Without safety, the result is groupthink or silence.

5. **Manage participation actively**: Use individual writing, round robin, and small groups to draw out quieter participants. Use time limits and parking lots to manage those who dominate.

6. **Decide how decisions are made**: Consensus, consent, majority vote, or delegation. Announce the method upfront to avoid "I thought we decided, but nothing happened."

7. **Track outputs visibly**: Shared board, live doc, or sticky notes so everyone sees the same thing. Assign a scribe. Invisible outputs are easily lost.

8. **Close with clarity**: State what was decided, who does what by when, what is still open, and how the group will communicate.

**Common pitfalls:**

- ❌ **No agenda**: Meetings drift, go long, participants unclear on purpose. Always have agenda (even 3 bullets).
- ❌ **Wrong people**: Decision-makers absent, too many observers, missing key stakeholders. Right people > right process.
- ❌ **Too much content**: 10 topics in 60 min = shallow on all. Better: 2-3 topics, go deep, make progress.
- ❌ **Facilitator dominates**: Facilitator should guide process, not content. Reduce own talking, ask questions, stay neutral.
- ❌ **No breaks**: 2+ hours without break → diminishing returns. Break every 60-90 min (5-10 min).
- ❌ **Ignoring energy**: Pushing through low energy → poor output. Use energizers, adjust pace, or stop early.

## Quick Reference

**Key resources:**
- **[resources/template.md](resources/template.md)**: Session design template, agenda builder, logistics checklist, closing template
- **[resources/methodology.md](resources/methodology.md)**: Pattern selection guide, agenda design principles, facilitation techniques, handling difficult dynamics, decision-making methods
- **[resources/evaluators/rubric_facilitation_patterns.json](resources/evaluators/rubric_facilitation_patterns.json)**: Session quality criteria (objectives clarity, participation balance, decision clarity, time management)

**Decision-making methods**:
- **Consensus**: Everyone must agree (slow, high buy-in, use for high-stakes or high-impact decisions)
- **Consent**: No one objects / "safe to try" (faster than consensus, Sociocracy)
- **Majority vote**: >50% wins (quick, can leave minority feeling unheard)
- **Advisory**: Input from group, decision by one person (fast, accountable, use when decision-maker clear)
- **Delegation**: Empower subset to decide with constraints (scales well, trust required)

**Participation techniques**:
- **Round robin**: Each person speaks in turn (ensures equal airtime)
- **1-2-4-All**: Think alone → pairs → fours → whole group (builds ideas, safe for introverts)
- **Silent writing**: Sticky notes or shared doc, no talking (prevents groupthink, good for brainstorms)
- **Breakout rooms**: Small groups (3-5 people) discuss, report back (scalable, increases participation)
- **Dot voting**: Each person gets N dots to vote on ideas (quick prioritization, visual)
- **Fist to Five**: Show fingers 0-5 to gauge agreement (quick temperature check)

**Energizers** (5-10 min):
- **Standup stretch**: Literally stand and stretch (blood flow)
- **Quick icebreaker**: "One word to describe how you're feeling", "What's on your desk right now?"
- **Music break**: Play upbeat song, encouraged to dance/move
- **Pair share**: 2 min with partner on non-work topic
- **Voting game**: Thumbs up/down rapid-fire questions ("Coffee or tea?")

**Timing guidelines**:
- **Daily standup**: 15 min (5-10 people, 1 min each)
- **1:1**: 30-60 min (half listening, half topics)
- **Team sync**: 60 min (updates, 1-2 discussion topics)
- **Brainstorm**: 30-60 min (diverge, cluster, dot vote)
- **Decision workshop**: 90-120 min (options, criteria, discussion, vote)
- **Retrospective**: 60-90 min (sprint), 2-3 hours (project)
- **Alignment session**: 2-4 hours (include breaks)
- **Design sprint**: 5 full days (or compressed to 2-3 days)

**Red flags** (adjust or stop session):
- >50% on laptops/phones (not engaged) → take break, energizer, or change format
- Same 2-3 people talking entire time → round robin, small groups
- Sidebar conversations → address directly ("Let's have one conversation"), or acknowledge and parking lot
- Confusion about purpose → stop, re-clarify objective, adjust agenda
- Running 30+ min over → apologize, reschedule rest, or ruthlessly cut content

**Inputs required:**
- **Objective**: What outcome do you need? (Decision, ideas, alignment, learning)
- **Participants**: Who? How many? Roles? Power dynamics?
- **Time**: How long? (Realistic estimate, not wishful thinking)
- **Constraints**: Location (remote/in-person), budget, cultural norms

**Outputs produced:**
- `facilitation-plan.md`: Session design (objective, agenda, materials, decision method, outputs)
- `session-notes.md`: What was discussed, decisions made, action items with owners

More from lyndonkl/claude

SkillDescription
abstraction-concrete-examplesBuilds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.
academic-letter-architectGuides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.
adr-architectureDocuments significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.
adverse-selection-priorProduces a Bayesian prior probability that an offered transaction is +EV for the recipient, given that the counterparty chose to propose it. Applies Akerlof market-for-lemons logic -- if they offered it, they believe it is +EV for them, so the prior that it is +EV for us is materially below 50%. Reusable across trade evaluation, waiver drops (another team dropping a player is also adverse selection), job-offer analysis, M&A, and any "someone offered me this" situation. Use when you receive an unsolicited trade/offer/proposal, analyzing incoming trade prior, evaluating why a counterparty proposed a deal, or when user mentions adverse selection, market for lemons, why did they offer this, incoming trade prior, they proposed it, Bayesian adjustment on received offer.
alignment-values-north-starCreates actionable alignment frameworks that give teams a shared North Star (direction), values (guardrails), and decision tenets (behavioral standards). Enables autonomous decision-making while maintaining organizational coherence. Use when starting new teams, scaling organizations, defining culture, establishing product vision, resolving misalignment, creating strategic clarity, or when user mentions North Star, team values, mission, principles, guardrails, decision framework, or cultural alignment.
analogy-weight-checkFor every analogy in a substacker draft, verifies it carries mechanical weight — the analogy does real work explaining the mechanism, not merely decorates it. Cross-references analogy-catalog.md for novelty (is this analogy reused from a prior post?) and domain fit (biology > organizational > sports preferred; physics/military disfavored). Use whenever an analogy appears in the draft. Trigger keywords: analogy weight, decorative, mechanical weight, reused analogy, catalog check, metaphor check.
answer-uncomfortable-questionTakes one strategic question about substacker ("should we launch paid?", "is this section dead?", "are we writing for the wrong audience?") and produces the mandatory evidence + reasoning + downside triad plus a recommendation. Used 3 times per Growth Strategist review. Trigger keywords: uncomfortable question, strategic question, evidence reasoning downside, triad.
attribute-performanceFor each substacker post that materially over- or under-performs the rolling baseline (|z| ≥ 1.0), produces a plain-English attribution paragraph with calibrated confidence (high / medium / low / unexplained). Considers subject-line effect, topic zeitgeist, external share, day-of-week, length effect, and audience-notes signals. Labels unexplained outliers explicitly rather than fabricating a story. Use after compute-baseline when outlier posts exist. Trigger keywords: attribution, why did this post work, outlier explanation, performance analysis.
auction-first-price-shadingComputes the optimal shaded bid for a first-price sealed-bid auction given a true private value, an estimate of the number of competing bidders N, and a value-distribution assumption. Implements the `(N-1)/N` equilibrium shading rule for uniform private values, adjusts for log-normal or empirical value distributions, layers a risk-aversion adjustment, and caps output against the bidder's remaining budget. Domain-neutral auction theory reusable across fantasy sports (baseball FAAB, NBA/NHL waiver auctions), prediction-market limit sizing, sealed procurement bids, and any blind-bid context. Use when user mentions "first-price auction bid", "sealed bid shading", "(N-1)/N", "FAAB bid amount", "auction shading", "optimal bid first-price", "bid for sealed-bid", "blind bid sizing", or when downstream logic needs a principled shade factor rather than an ad-hoc heuristic.
auction-winners-curse-haircutApplies a Bayesian haircut to a bid valuation for common-value auctions where winning is itself evidence the bidder over-estimated. Takes a raw valuation, a value-type classification (common_value / private_value / mixed), the number of informed bidders N, and a signal-dispersion estimate, and returns an adjusted valuation. Domain-neutral and reusable across fantasy FAAB, prediction markets, M&A bids, ad-auction budgets, and any generic bidding context. Use when user mentions "winner's curse", "common value auction", "valuation haircut", "adverse valuation", "Bayesian bid adjustment", or "over-paying in auction".