Workshop facilitation
Skill anotb/management-consulting-plugin/skills/workshop-facilitation
Management consulting skills for Claude Code, Cowork, Codex, and other agents. Strategy, operations, and transformation workflows for the full engagement lifecycle.
npx -y skills add anotb/management-consulting-plugin --skill workshop-facilitationAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
What its author says it does
Copied from the file, not written here
Design and facilitate consulting workshops: strategy offsites, design thinking sessions, innovation sprints, and discovery workshops. Use when planning client-facing facilitated sessions, running stakeholder alignment or prioritization exercises, designing working sessions for strategy development, or building facilitation guides and pre-work. Covers objective-setting, participant planning, methodology selection, agenda design, facilitation technique, and post-workshop follow-through.
The file declares its own license as MIT. That is the author’s claim about this one file, and it is not the same thing as the license GitHub reports for the repository, which is listed with the other numbers below.
SKILL.md
25.1 KB, as published. Nobody here has run it
Workshop Facilitation
Design, plan, and run strategy workshops, design thinking sessions, and innovation sprints. This covers structured working sessions at any point in an engagement. For the broader engagement launch process (kickoff, discovery, stakeholder mapping), see engagement-setup. The lifecycle here runs objective-setting, participant planning, pre-work design, methodology selection, agenda design, facilitation technique, and follow-through.
A workshop is a decision-forcing device, not a meeting with sticky notes. Every design choice below serves one goal: get the right people to produce and commit to outputs they could not have produced alone. Design backward from the decision.
Before You Begin
Workshop design fits the actual context or it fails. Confirm before designing:
- What is the objective, and what specific decisions or outputs must the session produce?
- Who are the participants (seniority mix, headcount, in-person vs. virtual)?
- How much time is available, and what format constraints apply?
Do not invent participant names, organizational dynamics, or pre-existing tensions. Ask who will be in the room and what the group dynamics look like. Fabricated dynamics produce a facilitation plan that breaks on contact with the real group.
Workshop Planning
Define Objectives
Answer these before designing anything:
- Why is this workshop needed? What decision, alignment, or output does it serve?
- What does success look like? Name concrete deliverables. "Productive discussion" is not a deliverable.
- Who needs to be in the room? And who explicitly does not.
- What format fits the constraints? In-person, virtual, or hybrid, and how long.
If you cannot name the decision the workshop forces, you do not have a workshop. You have a status meeting. Redesign or cancel.
Participant Planning
Map participants before designing the agenda. The design accommodates who is actually in the room, not who you wish were there.
| Dimension | Why It Matters |
|---|---|
| Decision makers | They approve outcomes. Design explicit decision points for them. |
| Influencers | They shape discussion. Give them structured airtime so they shape it on your terms. |
| Subject matter experts | They supply input. Design activities that extract their knowledge, not lectures that broadcast it. |
| Skeptics | They challenge ideas. Plan for productive challenge, not shutdown. |
| Introverts | They will not volunteer. Design silent-first activities. |
| Remote participants | They are disadvantaged by default. Over-design for their inclusion. |
Managing the CEO / Most Senior Leader
The most senior person in the room requires deliberate role management. Their default behavior shapes the whole session. This is where facilitation judgment earns its fee, so handle it precisely.
When they should speak:
- Opening: set context, signal importance, define the decision they need from the group.
- Closing: confirm decisions, signal commitment, assign accountability.
- When explicitly invited to share a perspective the group needs.
When they should NOT speak:
- During ideation and brainstorming. Their input kills divergent thinking.
- During initial sharing rounds. It anchors everyone to their position.
- While evaluating options. Others self-censor around a known preference.
How to manage it:
- Brief the leader before the session: "Your silence during brainstorming is a gift to the group. You will have dedicated time to react and decide."
- Use "juniors first" sharing order during evaluations.
- Use anonymous voting before revealing preferences.
- If they jump in too early: "Let's capture that. I want to hear from the rest of the group first, then we'll come back and synthesize."
- Give them a specific role (for example, "guardian of the customer perspective") to channel their energy productively.
The reframe that works: position their restraint as leadership, not silence. Senior leaders comply when holding back reads as a power move rather than a muzzle.
Pre-Work Design
Well-designed pre-work shifts cognitive load out of the workshop and into individual prep time. It makes session time dramatically more productive.
| Type | Purpose | Best For | Timing |
|---|---|---|---|
| Reading pack | Shared context and baseline knowledge | Strategy offsites, design reviews | Send 5-7 days before; keep under 20 pages |
| Survey / questionnaire | Surface perspectives before the room, identify alignment gaps | Alignment workshops, retrospectives | Send 7-10 days before; allow 3-5 days to complete |
| Individual reflection prompts | Force thinking before groupthink takes over | Innovation sessions, strategy decisions | Send 3-5 days before; 3-5 focused questions max |
| Data analysis or homework | Produce artifacts the workshop builds on | Working sessions, design sprints | Send 5-7 days before; assign specific outputs |
| Stakeholder interviews | Gather input from people not in the room | Discovery workshops, strategy alignment | Complete 1-2 weeks before |
Using pre-work in the session:
- Open with a summary of findings (5-10 min): "Here's what we heard."
- Use survey results to frame the agenda: "70% of you said X, 30% disagree. That gap is what we're here to resolve."
- Have participants share individual reflections in pairs before group discussion.
- Never ignore pre-work. If people did it and you do not reference it, they will not do it next time.
Completion reality: expect 60-70% completion (a directional planning estimate; ask the client sponsor how their team historically responds). Design the session so it works without pre-work but is sharper with it. Keep a 5-minute catch-up option for those who skipped it.
Format Considerations
| Format | Best For | Watch Out For |
|---|---|---|
| In-person | Deep collaboration, trust-building, complex decisions | Travel cost, scheduling difficulty |
| Virtual | Global teams, speed, accessibility | Fatigue after 90 min, harder to read the room |
| Hybrid | Mixed locations, real-time interaction | Remote participants becoming second-class citizens |
| Async-first | Reflection time, global time zones, pre-work | Loses energy and spontaneity |
For virtual and hybrid sessions: test all technology beforehand, staff dedicated tech support, and build in 50% more breaks than you think you need.
Workshop Methodologies
Select based on the outcome you need, not on what sounds impressive to the client.
Design Thinking
Best for: user-centered innovation, new product concepts, service design.
EMPATHIZE → DEFINE → IDEATE → PROTOTYPE → TEST
│ │ │ │ │
[User [Point of [Brain- [Build [Learn
Research] View] storm] It] & Iterate]
Half-day minimum, full day preferred. It requires real user data or customer insight as input. Running design thinking on assumptions produces confident nonsense.
Design Sprint (Google Ventures model)
Best for: fast decision-making, validating ideas quickly, aligning a team on direction.
DAY 1: Map DAY 2: Sketch DAY 3: Decide DAY 4: Prototype DAY 5: Test
[Understand] [Concepts] [Choose] [Build] [Validate]
Compressed 3-day and 2-day variants work but sacrifice depth. The 5-day version produces real user-tested prototypes. It requires a dedicated sprint team and a single clear decider.
Strategy Offsite (1-Day)
Best for: annual planning, strategic direction, competitive positioning.
CONTEXT → ANALYSIS → OPTIONS → DECISION → COMMITMENT
│ │ │ │ │
[Where [Where [Where [Where [How
we are] we are we can we will] we get
(deep)] go] (choose) there]
Full day minimum. The common failure mode: spend all day on context and analysis, then cram decisions into the last hour. Protect decision time as if it were the only thing on the agenda, because it is.
Strategy Offsite (2-Day)
Best for: comprehensive strategy development, complex multi-option decisions, deep alignment.
The 2-day format is substantially more effective than a single day for complex decisions. Overnight processing produces materially better Day 2 thinking. This is the highest-leverage methodology choice in the skill, so design it with care.
Day 1: Diverge (Context + Options)
09:00 Opening & Objectives [30 min]
09:30 External Context (market, competitive, customer) [90 min]
11:00 Break [15 min]
11:15 Internal Context (performance, capabilities, gaps) [75 min]
12:30 Lunch [60 min]
13:30 Strategic Options Generation [90 min]
15:00 Break [15 min]
15:15 Options Deep Dive (breakout groups) [90 min]
16:45 Day 1 Synthesis & Overnight Reflection [30 min]
17:15 Close (dinner optional but valuable)
Day 2: Converge (Evaluation + Commitment)
09:00 Overnight Reflections (round-robin, 2 min each) [30 min]
09:30 Options Evaluation Against Criteria [90 min]
11:00 Break [15 min]
11:15 Decision Session (structured debate + vote) [75 min]
12:30 Lunch [45 min]
13:15 Execution Planning (initiatives, owners, timeline) [90 min]
14:45 Break [15 min]
15:00 Commitment & Accountability [60 min]
16:00 Close [15 min]
Multi-day design principles:
- End Day 1 with divergence, not convergence. Let people sleep on unresolved options. Overnight processing is real. Do not force premature closure to feel productive.
- Manage Day 2 energy. Day 2 starts slower. The overnight reflection round does double duty: it surfaces new thinking and it warms the group back up. Do not skip it.
- Treat Day 1 dinner as a design element. Informal conversation over dinner resolves tensions and builds alignment that structured sessions cannot. Seat people deliberately (mix functions, pair skeptics with advocates).
- Protect Day 2 decision time. The temptation is to rehash Day 1 analysis. Set a hard rule: "Day 2 is for choosing and committing, not re-analyzing."
- Synthesize between days. The facilitation team spends 30-60 minutes after Day 1 close pulling out themes, naming unresolved tensions, and adjusting the Day 2 agenda.
Innovation Workshop
Best for: generating new ideas, breakthrough thinking, challenging assumptions.
WARM-UP → FRAME → GENERATE → EVALUATE → PRIORITIZE → PLAN
│ │ │ │ │ │
[Get [Define [Many [Screen [Select [Next
creative] the ideas] ideas] best] actions]
challenge]
Half day to full day. Quantity of ideas matters early, quality filtering comes later. Warm-up exercises are mandatory. They shift people out of operational thinking, and skipping them yields a room full of incrementalism.
Discovery Workshop
Best for: understanding current state at project kickoff, surfacing stakeholder perspectives.
Suggested flow (half day):
- Business Context (60 min): company overview, strategic priorities, current challenges.
- Stakeholder Perspectives (60 min): round-robin sharing, theme identification, priority ranking.
- Journey Mapping (60 min): map key processes, identify pain points and gaps, spot quick wins.
- Opportunity Framing (60 min): problem statement development, success criteria, next steps.
Key outputs: current state assessment, challenge prioritization, opportunity shortlist, project charter draft.
Strategy Alignment Workshop
Best for: getting leadership aligned on direction when there are competing views.
Suggested flow (full day):
Morning, Current State (3 hours):
- External Reality (60 min): market trends, competitive forces, customer insight.
- Internal Reality (60 min): performance review, capability assessment, digital maturity.
- Strategic Choices (60 min): options review, trade-off decisions, preliminary direction.
Afternoon, Future State (3 hours): 4. Strategic Direction (60 min): strategic narrative, pillars, success definition. 5. Execution Priorities (60 min): key initiatives, resource allocation, timeline. 6. Commitment (60 min): role assignments, governance, next steps.
Key outputs: agreed direction, strategic pillars, initiative priorities, action assignments.
Agenda Design
Timing Principles
- Never exceed 90 minutes without a break in-person.
- Never exceed 60 minutes without a break for virtual sessions.
- Allocate 60% to activities, 20% to transitions and breaks, 20% to opening, closing, and synthesis.
- Front-load divergent thinking. Morning energy suits creative work.
- Schedule decisions after breaks. Fresh minds make better choices.
- Build in buffer. Every activity runs 10-15% longer than planned.
Standard Agenda Template
08:30 Registration & Coffee
09:00 Opening & Objectives [Facilitator] [30 min]
09:30 Context Setting [Presenter] [30 min]
10:00 Activity 1 [Facilitator] [60 min]
11:00 Break [15 min]
11:15 Activity 2 [Facilitator] [90 min]
12:45 Lunch [45 min]
13:30 Activity 3 [Facilitator] [90 min]
15:00 Break [15 min]
15:15 Synthesis & Decisions [Facilitator] [60 min]
16:15 Next Steps & Close [Facilitator] [30 min]
Activity Design Template
For each activity, define:
- Purpose: why it exists (tie it back to a workshop objective).
- Method: how it works, step by step.
- Inputs: what participants need to have or know before starting.
- Outputs: the tangible thing produced.
- Time: duration with a step-by-step breakdown.
- Facilitation notes: common failure modes and what to watch for.
When you build a real agenda, fill each activity block with 2-3 sentences of reasoning: what it produces, why it sits where it does, and the failure mode you are guarding against. A one-word label is a placeholder, not a design.
Facilitation Techniques
Opening
Set the tone in the first 5 minutes. Cover:
- Why we are here (purpose, not logistics).
- What we will produce by the end (specific deliverables).
- Ground rules (be present, build on ideas, respect time, all voices matter).
- For virtual and hybrid: quick tech check, camera expectations.
Managing Group Dynamics
This table is the facilitator's field manual. Each response is a scripted move, not a principle. Learn them cold.
| Challenge | Response |
|---|---|
| Dominant participant | "Let's hear from someone who hasn't spoken yet." Or switch to structured rounds. |
| Quiet group | Silent writing before discussion. Go around the room explicitly. |
| Conflict between participants | Acknowledge both views: "You're both raising real points. Let's capture both and score them against our criteria." |
| Off-topic tangent | "Good point. I'm putting it on the parking lot so we don't lose it. Let's stay on [current topic]." |
| Energy drop | Switch format. Stand up. Run a quick poll. Take an unscheduled break. |
| Time pressure | "We need to move. Capture remaining thoughts on sticky notes, and let's focus on decisions." |
| HiPPO effect (highest-paid person dominates) | Anonymous voting. Juniors share before seniors. Pre-collect input. Brief the senior leader beforehand on their role. |
Decision-Making Methods
| Method | When to Use | How It Works |
|---|---|---|
| Dot voting | Ranking many options quickly | Each person gets 3-5 dots, places them on preferred options |
| Thumbs up/down/sideways | Quick alignment check | Up = agree, down = disagree, sideways = concerns |
| Multi-voting + discussion | Complex decisions with trade-offs | Vote first, then discuss the top 3-5 options |
| Gradients of agreement | When consensus matters | 1-5 scale from "fully support" to "can't live with it" |
| Decision rights matrix (RACI) | When authority is unclear | Clarify who decides, who is consulted, who is informed |
Transitions
Script your transitions. The story arc of a workshop breaks when transitions go sloppy.
- Between activities: "Here's what we just accomplished [summary]. Now we build on it by [next activity purpose]."
- At midpoint: "We're halfway. So far we've [summary of outputs]. Here's what the second half has to deliver."
- Before decisions: "The analysis is done. Now we choose. Here's what we're deciding and how."
Closing
Never let a workshop trail off. Run a structured close:
- Summary of outputs: what we produced.
- Decisions made: what was decided, and by whom.
- Action items: specific actions, owners, due dates. Vague commitments do not count.
- Feedback: quick round or one-word checkout.
- Clear end: thank participants, state the next communication.
Hybrid Workshop Design
Hybrid is the hardest format to facilitate well. Remote participants are disadvantaged by default, and the facilitator has to actively compensate.
Non-negotiable practices:
- Camera on for everyone (room camera showing the full room, individual cameras for remote).
- A dedicated "remote advocate" in the room who monitors chat and speaks for remote participants.
- A digital whiteboard as the primary workspace, never a physical one remote people cannot see.
- All materials shared digitally before the session.
- Explicit turn-taking that includes remote voices: "Before we continue, let me check in with our remote participants."
- Polls and voting through digital tools, never hand-raising that remote cannot see.
Post-Workshop Follow-Through
The real workshop happens after. Outcomes without follow-through are theater.
Immediate (same day)
- Send a thank-you to participants.
- Share key takeaways and photos or screenshots of outputs.
- Confirm action items with owners.
Within one week
- Distribute the full summary (decisions, action items, key outputs).
- Share all materials and digital artifacts.
- Send the recording if virtual.
- Schedule follow-up meetings for action items.
Within two weeks
- Track action item progress.
- Gather feedback on workshop effectiveness.
- Document lessons learned for the next one.
Workshop Summary Template
# Workshop Summary: [Name]
Date: [Date]
## Participants
[Names and roles]
## Objectives and Whether Achieved
[Objective: achieved / partially / not achieved]
## Key Outputs
[Deliverables produced]
## Decisions Made
[Decision: rationale: decision maker]
## Action Items
| Action | Owner | Due Date | Status |
|--------|-------|----------|--------|
## Parking Lot (items deferred)
[Topics captured but not addressed]
## Next Steps
[Next milestone, date, owner]
Workshop Risk Register
Plan for what goes wrong. The facilitator who says "that won't happen" hasn't run enough workshops. Fill each response cell with the actual move you will make, not a category.
Common Risks and Responses
| Risk | Impact | Response |
|---|---|---|
| Scoring or voting ties | Decision stalls, group loses momentum | Pre-define the tiebreaker before voting: decision-maker breaks the tie, re-score the tied items only on weighted criteria, or reframe with "which option do we regret NOT pursuing?" |
| Hostile or disruptive participant | Derails discussion, intimidates others | Name the behavior privately at a break: "I need your expertise, but the way you're pushing back is shutting others down." If it continues, redirect: "Let's log that as a dissenting view and move on." Never fight in public. |
| Senior sponsor ignores the pre-brief | Leader speaks first, anchors the room, kills divergence | Interrupt gently and early: "Thank you. I'd love to come back to that once we've heard from the group." Re-brief at the next break: "We'll get more out of the room if other voices go first. You'll have dedicated time to react." |
| A breakout group produces nothing useful | Uneven outputs undermine synthesis | Assign a process observer per breakout. Check in at the midpoint. If a group is stuck, hand them a concrete prompt or redistribute members. |
| Pre-work completion near zero | Session starts cold, agenda timing breaks | Run a 10-minute crash course on the essential context. Shorten pre-work-dependent activities, extend context-setting. Never shame people for skipping it. |
| Key decision-maker leaves early | Decisions cannot be ratified | Get their input on decision items first. Front-load their participation. If they must leave before decisions, secure explicit delegation: "Who holds your authority on items 3 and 4?" |
Technology Failure Backup
Technology will fail. Have a plan that does not need it.
| Technology | Failure Mode | Backup |
|---|---|---|
| Projector / screen | Won't connect, bulb dies | Print key slides (6-up on paper). Facilitate from a whiteboard. The slides are your notes, not the session. |
| Digital whiteboard (Miro, Mural) | Platform down, no access | Physical sticky notes on a wall. Photograph results. Carry sticky notes and markers to every session. |
| Video conferencing (hybrid) | Audio or video drops for remote | Dial-in phone number as backup. Assign an in-room buddy to text updates. If remote is fully lost, pause and solve, or reschedule the remote portion. |
| Polling / voting tool | Tool crashes mid-vote | Paper ballots or hand-raising. For anonymous voting, have people write on cards and collect face-down. |
| Wi-Fi | Network down | Mobile hotspot. Pre-download all materials. Any activity needing live internet gets an offline alternative. |
General rule: if a single technology failure can derail the whole session, the design is fragile. Every digital activity needs a 30-second analog fallback you have already worked out.
Cultural Facilitation Differences
Facilitation norms vary across cultures. These are tendencies, not rules, and they are directional. Ignoring them produces bad sessions.
| Dimension | Western / Low-Context Tendency | East Asian / High-Context Tendency | Adaptation |
|---|---|---|---|
| Disagreement | Direct, in the room | Indirect, often after the session | In high-context cultures, build 1:1 channels (breaks, written input) for dissent. Do not read silence as agreement. |
| Speaking order | Whoever has something to say | Deference to seniority | Use explicit rounds ordered by seniority (junior-first or senior-first depending on the goal) rather than open floor. |
| Decision-making | Vote and move on | Consensus-building, may need multiple sessions | Budget more time for convergence. A "decision" in the room may need offline confirmation. |
| Brainstorming | Verbal, spontaneous | Written, considered | Default to silent-first activities everywhere (they travel well). Never rely solely on "shout it out." |
| Time | Agenda is a commitment | Agenda is a guide | In relationship-oriented cultures, protect relationship-building time (longer breaks, meals) and flex the agenda. |
Bottom line: when in doubt, use structured, written-first activities with explicit turn-taking. They hold up across every cultural context. Open-floor, verbal-first formats fail cross-culturally most often.
Behavioral Principles
- Energy management is facilitation. Watch group energy. Switch formats, break, or add movement when it dips. A tired group produces nothing useful.
- Silence is productive. Allow 10-15 seconds after a question. Resist filling every pause. The best insights arrive after the obvious answers are spent.
- Design for introverts first. Silent writing before sharing captures all voices, not only the loudest. "Think, write, share" almost always beats "who wants to go first?"
- Follow-through is the deliverable. Actionable commitments outrank polished in-session artifacts. A workshop that produces beautiful outputs and no follow-up wasted everyone's time.
- Timebox ruthlessly. Sessions that run over lose energy and credibility. End on time. If you fall behind, cut content, never the closing or the decision.
- Keep backup activities ready. When an activity falls flat or finishes early, you need alternatives on hand. Preparation is what separates good facilitators from great ones.