What workshop facilitation is and why it matters NN/g
A workshop is a method to collaboratively solve a problem. That single definition separates it from every meeting you've ever sat through: meetings share or exchange information, workshops produce outcomes. Meetings are measured in hours and allow shallow coverage of many issues. Workshops are measured in half-days or days and go deep on one focused problem. The deliverable is not a set of notes — it's a set of decisions, artifacts, or aligned directions that didn't exist before the session started.
Facilitation is the discipline that makes workshops work. To facilitate means to bring about an outcome by providing indirect, unobtrusive guidance. The facilitator is not the expert, not the decision-maker, and not the presenter. The facilitator designs the structure, manages the energy, draws out contributions from everyone in the room, and connects the output to what happens next. Without skilled facilitation, workshops devolve into the meeting they were supposed to replace — the loudest person dominates, the group drifts, and nothing gets decided.
Four goals define the facilitator's role: encourage full participation, promote mutual understanding, foster inclusive decisions, and cultivate shared responsibility. Every technique, activity, and structural choice in a workshop should serve at least one of these goals. If it doesn't, it's filler.
Why this matters for your projects
Workshops are the primary mechanism through which cross-functional alignment actually happens in UX and product work. Discovery workshops align teams on what to build. Empathy workshops shift stakeholders from features-first to users-first thinking. Design workshops generate ideas from varied perspectives. Prioritization workshops create shared commitment. Critique workshops improve designs before engineering commits resources. If you can't facilitate a workshop, you're relying on slide decks and meetings to create alignment — and that almost never works for complex problems.
The meetings-vs-workshops distinction
Recognizing when you need a workshop versus when a meeting will do saves time and political capital. Meetings work when you need to broadcast information, give a status update, or make a quick decision where one person has authority. Workshops work when you need diverse input on a complex problem, when multiple perspectives must be integrated, or when the group needs to co-own the outcome for it to stick. If you could achieve the goal by sending an email, you don't need a workshop. If people will resist an outcome they weren't part of creating, you do.
Meetings require a presentation and an outline. Workshops require an agenda, planned activities, prepared materials, and pre-built buy-in from participants. The preparation ratio is roughly 43 hours of design time for every 1 hour of facilitated content — a number that surprises people who think you can wing a workshop with sticky notes and good intentions.
Workshop structure: the Open–Explore–Close model NN/g
Every workshop — regardless of type, length, or topic — follows three phases. This model comes from the Gamestorming framework (Gray, Brown, Macanufo) and maps to how groups naturally process complex problems. Understanding it lets you diagnose where a workshop is going wrong in real time and course-correct.
Open (divergent): Frame the situation and create boundaries. The group gathers information, generates ideas, and maps out the scope of the problem. Thinking is expansive. The facilitator's job is to establish boundaries, amplify diverse ideas and perspectives, and encourage full participation. Challenges in this phase: getting everyone aligned, encouraging quiet people to speak, and preventing premature judgment of ideas.
Explore (emergent): Navigate, combine, and interpret ideas to discover something new. The group dives deeper into generated ideas, uncovers patterns, examines relationships, and strengthens promising directions. Thinking is investigative. The facilitator's job is to promote mutual understanding, integrate multiple perspectives, and alleviate anxiety when the group feels stuck. Challenges: ensuring everyone is talking about the same thing, balancing differences of opinion, and managing fatigue.
Close (convergent): Find an endpoint through prioritization, voting, or comparison. The group makes decisions, reaches agreement, and defines next steps. Thinking is evaluative. The facilitator's job is to foster inclusive decisions, strengthen good ideas, and capture and communicate the action plan. Challenges: making sure everyone is part of the decision, continuing to refine rather than settling for the first option, and ensuring momentum carries past the workshop.
Practical tip
Many workshops fail because they spend too long in the Open phase and rush the Close. Timebox your Opening activities aggressively — the energy and urgency of a tight timebox often produces better divergent output than an open-ended brainstorm. Then protect the Close phase: that's where decisions happen, and decisions are the whole point.
Using constraints to increase productivity
Constraints are the facilitator's most powerful structural tool. There are four types, and effective workshop design uses all of them:
Rules: How participants interact — one idea per sticky note, silent generation before discussion, no devices during activities. Rules prevent the default social dynamics (extroverts dominating, anchoring on the first idea) from undermining the process.
Boundaries: Limits on time and space — five minutes per activity round, one whiteboard per group, three words maximum per sticky note. Boundaries create productive pressure and prevent scope creep within activities.
Artifacts: Physical or digital objects that hold information about the activity — sticky notes, templates, matrices, canvases. Artifacts externalize thinking so the group can see, move, and manipulate ideas collectively rather than keeping them trapped in individual heads.
Goals: An end-state that everyone tries to attain — "by the end of this activity, we'll have 20 ideas on the wall" or "we need to leave with a ranked list of five priorities." Goals give the group a shared target and make progress visible.
The facilitator's role and mindset NN/g
The FACILITATE framework provides ten guidelines for how to show up as a facilitator. These aren't techniques — they're dispositions. Techniques can be learned in an afternoon; the facilitator mindset takes practice.
FACILITATE Framework Core Framework
Use when: preparing mentally for any facilitation role, or reflecting after a session on what to improve.
F — [Solicit] Feedback. Continuously ask the group how the process is working. Don't wait until the end. A — [Practice] Active Listening. Hear what people mean, not just what they say. Paraphrase back to confirm understanding. C — Create Space. Make room for quieter voices. Notice who hasn't spoken and invite them in. I — Improvise. The agenda is a plan, not a contract. Adapt when the group needs something different. L — Lean into the group purpose. When things go sideways, return to why you're here. I — If you don't know, say so. Credibility comes from honesty, not from having all the answers. T — Take everything as relevant. Even off-topic comments often contain useful signal. A — Avoid advice. Your job is to facilitate others' thinking, not to insert your own conclusions. T — To thine own self be true. Bring your authentic facilitation style rather than imitating someone else's. E — Embrace conflict. Disagreement is productive data, not a problem to shut down.
Common mistake
New facilitators confuse "neutral" with "passive." Neutrality means you don't advocate for specific outcomes or inject your own opinions into the content. It doesn't mean you sit back and let the group flounder. A good facilitator is extremely active — redirecting, timeboxing, creating space for quiet voices, summarizing, connecting — while staying out of the content itself.
The facilitator's toolbox: foundational activities NN/g
The toolbox has three layers: materials (what you work with), activities (what participants do), and techniques (how you manage the process). Activities are the backbone — each one maps to a specific phase of the Open–Explore–Close model.
Opening activities (divergent)
Post-up Foundational Activity
Use when: you need to generate a wide set of ideas that represent diverse perspectives quickly. 1–30 people, 10–30 minutes.
Each participant silently writes ideas on sticky notes (one idea per note), then posts them on a shared wall or board. The silent generation step is critical — it prevents anchoring on the first person's ideas and gives introverts equal space. After posting, the group reads and clusters the notes, which often transitions into affinity diagramming.
Brainwriting (6-3-5 variant) Foundational Activity
Use when: you want to generate and build on ideas through collaboration. 5–15 people, 30–45 minutes.
Participants silently generate ideas on a sheet, then pass the sheet to the next person who adds ideas inspired by what's already there. Each pass builds on and recombines previous thinking. Brainwriting outperforms verbal brainstorming because it eliminates production blocking (waiting for your turn) and evaluation apprehension (fear of judgment). Adapt the constraints freely: assign thinking hats per column, use it for concerns or assumptions instead of ideas, make it anonymous, or adjust time and space per round.
3-12-3 Brainstorm Activity
Use when: you want to use speed as a constraint to discourage overthinking. Up to 10 per group, 20–30 minutes.
Three minutes: generate a pool of characteristics or ideas — go fast, don't filter. Twelve minutes: pairs draw three random ideas from the pool and develop a concept to present. Three minutes: each pair presents. The compressed timing forces intuitive, lateral connections that longer brainstorms miss.
Exploring activities (emergent)
Affinity Diagramming Foundational Activity
Use when: you need to discover patterns by clustering information into relational groups. 1–20 people, up to 90 minutes.
Take the output of a post-up or brainstorm and silently sort items into groups based on natural relationships. Resist the urge to create categories first — let groups emerge from the data. Once clusters form, name each one. Affinity diagramming transforms a chaotic wall of ideas into a structured map of themes, which feeds directly into prioritization.
Landscape Mapping Foundational Activity
Use when: you need to create alignment between different activities, ideas, or perspectives. 3–10 people, 30–60 minutes.
Place items on a shared visual landscape — empathy maps, journey maps, or custom matrices. The spatial arrangement reveals relationships and gaps that lists miss. Particularly effective for mapping user experiences, stakeholder relationships, or project timelines where positioning relative to each other matters.
Wizard of Oz Activity
Use when: you want to uncover breaking points in an existing design or generate new ideas through simulation. 2 players plus observers, 30–60 minutes.
Create outlines of user interactions and system responses. One participant plays the user, one plays the system (responding only with pre-scripted options). Observers capture frustrations, gaps, and opportunities. This reveals where assumptions break down in ways that discussion alone can't surface.
Do-Redo-Undo Activity
Use when: you need to explore potential challenges and pitfalls of a strategy. 5–10 people, 30–60 minutes.
Brainstorm worst-case scenarios and mistakes. Rank the most damaging ones. Then address each through three lenses: Do (change the design to avoid the problem), Redo (provide a means for course correction), Undo (provide a way to reverse an action). Breaks linear thinking by forcing the group to consider failure modes before committing.
Reverse It Activity
Use when: you need to break out of the same ways of thinking about an existing problem. 5–20 people, 30–45 minutes.
Agree on a well-defined problem. Then articulate the opposite — the "anti-problem." Brainstorm solutions to the anti-problem. The inversion often reveals approaches and insights that direct problem-solving misses. Example: instead of "How do we make account setup easier?" ask "How do we prevent users from setting up their account?"
Closing activities (convergent)
Forced Ranking Foundational Activity
Use when: you need to create a clear, single ranked list that the group agrees on. 3–10 people, 30–60 minutes.
Prioritize items against defined criteria. Methods include dot voting (quick heat-mapping of preferences), the $100 Test (groups allocate a fixed budget across options, forcing trade-offs and capturing reasoning), and the NUF Test (scoring each idea 0–10 on Novelty, Usefulness, and Feasibility, then tallying). Choose based on how much discussion you want: dot voting is fast and low-discussion, the $100 Test generates rich rationale conversation, and the NUF Test provides a structured multi-criteria evaluation.
Impact/Effort Matrix Activity
Use when: you need to evaluate the potential impact and effort of ideas before committing to them. Small groups, 30 minutes.
Create a 2×2 matrix with effort on one axis and impact on the other. Have participants map ideas as they present them, then openly discuss positioning. The visual layout makes trade-offs immediately obvious — high-impact/low-effort items are clear wins, while low-impact/high-effort items can be deprioritized or killed.
Role Playing Foundational Activity
Use when: you need to build empathy and promote understanding of other perspectives. Small groups of 3–5, 30–60 minutes.
Participants adopt specific user personas, stakeholder roles, or thinking hats (de Bono's Six Thinking Hats or Google's design sprint variant) and evaluate decisions or designs through that lens. Particularly effective for critique workshops and for helping non-designers understand user frustrations firsthand.
The facilitator's toolbox: core techniques NN/g
Techniques are micro-interventions you deploy in real time. Unlike activities, which are planned into the agenda, techniques are situational — you reach for them when you notice something happening (or not happening) in the room.
Paraphrase: Restate what you heard in roughly the same number of words. Watch the speaker's reaction — if they nod, you understood. If they correct you, you surfaced a nuance that might have been missed. Paraphrasing shows contributions were heard and creates shared understanding.
Create Expansion: Help others clarify and develop their ideas further. Ask open-ended, non-directive questions: "Tell me more about that," "Can you give an example?" "What do you mean by...?" Expansion questions are neutral — they don't steer toward a particular answer.
Encourage: Create openings for people to participate without putting them on the spot. "Is this raising questions for anyone?" "Has that happened before in anyone else's experience?" Give people time to respond before interjecting — silence is an invitation, not a problem.
Balance: When one perspective dominates, invite different viewpoints. Stay aware that silence doesn't equal agreement. "We've heard a lot of potential challenges. Anyone want to add a potential benefit?" Draw out silent views with non-threatening, probing questions.
Link: Help someone connect a seemingly off-topic comment to the discussion. Paraphrase the comment, then ask: "What's the connection you're seeing between that and the topic at hand?" If it's truly irrelevant, capture it in the Parking Lot — a visible space for valuable-but-not-now items.
Intentional Silence: Maintain eye contact and focus. Don't speak, don't nod. Wait patiently. People naturally dislike conversational pauses and will fill them — often with the most thoughtful contribution of the session. This is the hardest technique for new facilitators because it feels uncomfortable, but it's one of the most powerful.
Common Ground: When sides are strongly opposed, summarize the main differences, call out areas of agreement, and check for accuracy. This prevents conflict from becoming personal by reframing it as a problem the group can solve together.
Summarize: As you shift topics, restate the main themes and key points. "I heard three major themes. [Name them.] Does anyone want to add anything before we move on?" This consolidates thinking and creates clean transitions.
Create Space: Watch for body language — someone leaning forward, opening their mouth, looking like they want to speak. Invite them in: "Was there something you wanted to say?" This is different from Encourage (which is general) — Create Space targets a specific person you've noticed.
Handling dominating participants NN/g
Three types of dominators show up regularly, and each requires a different approach:
The Helpful HIPPO (highest-paid person's opinion): A participant with authority who unintentionally intimidates others and inhibits contributions simply by being in the room. They usually don't realize they're dominating. Counter-strategy: Redirect — point back to the group purpose and timeline, use structured activities that give everyone equal airtime (silent post-up, round robin).
The Eager Enthusiast: An overly passionate participant who inadvertently dominates through sheer energy and volume. They care deeply and aren't trying to silence others. Counter-strategy: Balance — invite nondominant participants to contribute in structured ways (quotas: each person gets three contributions), round-robin turns, or pair work before group sharing.
The Enlightened Expert: A subject matter expert who over-shares tangential knowledge or background context. Counter-strategy: Silence — remove verbal contributions temporarily by switching to silent activities (silent post-up, brainwriting). This ensures mutual participation from everyone without singling out the expert.
Practical tip
Most domination happens because someone doesn't feel heard, not because they're trying to take over. Before deploying structural countermeasures, try paraphrasing their point back to them and explicitly acknowledging the value of their contribution. Often that's enough — once they feel heard, they make space for others.
Five types of UX workshops NN/g
Each workshop type maps to a different stage in the UX project lifecycle. Understanding when to run which type is as important as knowing how to facilitate them.
Discovery Workshop Workshop Type
Use when: you're starting a project and need to understand the current state, gather existing knowledge, and build consensus on direction. Place in timeline: project initiation or phase kick-off.
Team members and critical stakeholders converge to surface what's known, identify assumptions, understand business requirements, and agree on milestones. The Assumption Smash playbook works well: ask "What do we already know about our users?" then sort answers into Facts (has a source) vs. Assumptions, identify which assumptions need validating, and surface additional gaps. Output: documented understanding of current state plus an action plan for what needs to be learned.
Empathy Workshop Workshop Type
Use when: you need to shift stakeholder perspective from features-first to users-first, or when sharing research insights to influence design direction. Place in timeline: after user research, before design kick-off, or during iterative testing.
Designers, researchers, and stakeholders create a shared understanding of user needs before designing solutions. The Missions, Mindframes & Methods playbook creates three swim lanes: Missions (high-level goals users want to accomplish), Mindframes (mental states and beliefs driving those goals), and Methods (features, content, or ideas that could help users accomplish their missions). Output: shared, documented understanding of user needs translated into design implications.
Design Workshop Workshop Type
Use when: you need to rapidly generate a wide set of ideas for a specific design challenge from diverse perspectives. Place in timeline: after research, at design kick-off, or when refining a chosen direction.
Cross-disciplinary team members sketch, present, critique, converge, and prioritize. The Crazy 8's playbook compresses ideation: fold paper into 8 rectangles, sketch 8 ideas in 5 minutes (Round 1), then develop one big idea in 5 minutes (Round 2), then storyboard the key user steps in 5 minutes (Round 3). Follow with group critique using dot voting, thinking hats, or sticky note comments. Output: prioritized set of design directions with shared ownership.
Prioritization Workshop Workshop Type
Use when: the team can't agree on direction, scope is creeping, or you need to weigh features against each other with stakeholder input. Place in timeline: after user research (to shape roadmap) or mid-design (to manage scope).
Key decision-makers collaboratively prioritize features, initiatives, or ideas. Use the NUF Test for a structured multi-criteria reality check, the Impact/Effort Matrix for visual trade-off analysis, or the $100 Test when you need rich discussion about relative value. Output: consensus on priorities with captured reasoning.
Critique Workshop Workshop Type
Use when: you need to evaluate designs against principles, user needs, or objectives. Place in timeline: at design checkpoints throughout iterative development.
A small, intimate group analyzes and improves a design. The Persona Hats playbook assigns each group a user persona, then each group does a cognitive walkthrough "wearing that hat" — capturing questions, frustrations, and opportunities from the assigned user's perspective. Output: agreement on design direction with user-centered critique from multiple perspectives.
Planning and designing a workshop NN/g
The Workshop Design Canvas
Resist the temptation to start by listing activities. Instead, work through the canvas in order: Goals → Questions → Processes. Goals are the desired outcomes or end results. Questions are what information needs to be gathered to reach those goals. Processes are the activities participants will do — and they come last, chosen specifically to answer the questions that serve the goals.
Effective workshops are systematic (planned, well-organized, with a goal and a method), objective (minimal facilitator or method bias), focused (on specific questions), and actionable (the results enable you to take action).
Three planning documents
Workshop Design: The facilitator creates a high-level session design — which techniques, which tools, which activities — in collaboration with the client or project sponsor. This is the strategic layer.
Workshop Agenda: The facilitator and client develop a draft agenda to ensure confidence in the approach. After revision, it's finalized and shared with all stakeholders and participants. This is the communication layer — participants see this.
Running Order Agenda (ROA): A detailed step-by-step process sheet with timeboxes, activity instructions, transition notes, and a supplies checklist. The ROA is only for the facilitator and is never shared with participants. This is the execution layer.
Common mistake
Skipping the ROA and facilitating from the participant-facing agenda. The agenda shows what happens — the ROA shows exactly how to make each thing happen, including what to say during transitions, when to announce time warnings, and what to do if an activity runs long. First-time facilitators who wing the execution layer almost always run over time or lose the thread between activities.
Establishing ground rules
Before any workshop begins, establish two things: Group Purpose (what you want to accomplish and walk out with) and Group Culture (the rules you'll abide by to get there). The most effective approach makes ground rules collaborative: divide participants into small groups, assign each a theme (Diversity, Respect, Confidentiality, Collaboration), have them create rules, then review and agree as a full group. Imposed rules feel like restrictions; co-created rules feel like commitments.
Conducting exercises: Explain → Execute → Examine NN/g
Every activity within a workshop follows a three-step facilitation model. This rhythm is what separates a well-facilitated activity from one that feels chaotic.
Step 1: Explain
Introduce the activity: describe how to do it, walk through the steps, define roles if applicable. Discuss context: why it's important and how it connects to the workshop goals. Answer clarifying questions. Critical rule: never state what will be learned as a result — stay neutral, avoid biasing statements, and let the activity produce its own insights. Keep explanations brief for experienced groups, more detailed for newcomers.
Step 2: Execute
Let participants carry out the activity. Remain out of focus unless you have an assigned role. Wander the room, answer questions, observe, and listen for comments you can surface during the debrief. If someone asks "Is this the right direction?" — reframe and redirect: "Does the whole team feel this is the right direction? What led you here?" Announce time at the halfway mark, the 5-minute mark, and 1 minute before the end.
Step 3: Examine
Present: Participants showcase work to the group. Predetermine presentation order and time per group. Ask questions that deepen understanding — and aim to have others in the room ask questions too. Don't fear silence — people need time to think. Reflect: Ask what participants got out of it, where they got stuck, what was hard or surprising. Repeat back comments you heard during execution to spark discussion. Connect: Link the activity output to what was previously learned and what comes next. Synthesize outputs, especially if they feed into subsequent activities.
Virtual workshop facilitation NN/g
Virtual workshops require structural changes, not just tool substitution. The core principles remain — Open/Explore/Close, constraints, the Explain/Execute/Examine model — but execution must adapt to the medium.
Engagement: Call participants by name. Assign roles (timekeeper, notetaker). Design activities that require participation from everyone — passive listeners disengage faster online. Use virtual whiteboards, polls, annotation tools, and chat. Keep sessions under 2 hours maximum; provide breaks in any session longer than 90 minutes.
Relationship: Include an icebreaker that helps participants connect as people. Divide larger groups into breakout rooms for discussion. Plan for facilitators and participants to connect briefly beforehand (sharing photos, connecting on LinkedIn). Build rapport through shared personal experiences.
Communication: Speak more slowly than normal. Use visual aids extensively. Check for understanding frequently. Use feedback tools that mimic body language — raised-hand icons, emoji reactions, status indicators.
Technology: Understand technical requirements and communicate them to participants in advance. Practice using the tools before the session. Build in time at the beginning for participants to test and practice with virtual tools. If more than 3 participants are co-located, assign a location facilitator for that group.
Common mistake
Applying an existing in-person Running Order Agenda to a virtual session without redesigning it. Virtual workshops need shorter activity cycles, more frequent check-ins, explicit transitions ("We're now moving to the Explore phase"), and structured turn-taking. Also: do not invite nonessential participants to virtual workshops — larger groups amplify disengagement online.
Post-workshop: follow-up and evaluation NN/g
Developing a follow-up plan
A workshop without a follow-up plan produces a spike of enthusiasm that decays within days. The output document should include: a reminder of the workshop's goal, an explanation of each activity and its purpose, key insights from each activity, photos or screenshots of artifacts wherever possible, and concrete next steps with owners and deadlines. Send this within 48 hours while the session is fresh.
Evaluating success
Use two complementary evaluation approaches:
Soft evaluation: Open-ended questions that capture feelings, perceptions, and learnings — "What did you learn from this experience?" "Which activity was of greatest value to you?" "What was not useful?" Soft evaluation surfaces qualitative insights about what worked and what to adjust.
SMART evaluation: Measurable outcomes evaluated against Specific, Measurable, Attainable, Results-oriented, Time-bound criteria — "Was [specific outcome] met? (Likert scale)" "To what percentage did we achieve [goal]?" SMART evaluation tells you whether the workshop achieved its objectives, not just whether people enjoyed it.
[Activities, techniques, or moments that produced strong engagement or outcomes]
[What you'd change next time — timing, activity selection, group dynamics]
[Unexpected moments and what they taught you about facilitation]
[Update activities and flow / Send follow-up and thank-yous / Update supplies list]
Real-world examples NN/g
Case study
Discovery workshop for an e-commerce customer experience project
A design consultancy ran a full-day discovery workshop at the start of a customer experience redesign. They organized the session around four goals: align on how the ideal experience is defined, understand key stakeholders, establish baseline understanding of the audience, and create an approach and process for working together. Activities included: customer experience definition and metrics brainstorm, current CX efforts overview, stakeholder mapping, rapid audience brainstorm with an assumption smash, as-is scenario mapping, and project timeline and ownership mapping.
Why it works: Each activity was chosen to answer a specific question that served a specific goal — not selected because it seemed fun or familiar. The assumption smash in particular prevented the team from moving forward on unvalidated beliefs about their users, saving weeks of potential misdirection.
Case study
Workshop sprint: five types in sequence
A product team ran a compressed workshop sprint over one month rather than treating each workshop type as a standalone event. Week 1: half-day discovery workshop to establish scope and alignment. Week 2: one week of user research. Week 3: half-day empathy workshop to share research findings, immediately followed by a half-day design workshop. Week 4: one month of iterative design with prioritization and critique workshops at checkpoints throughout.
Why it works: The team adapted the canonical workshop sequence to their real constraints — spreading activities across weeks, adjusting durations, and combining types. The key insight: you don't need to run each workshop type as a formal half-day event. Spread them out, adjust the sequence, or combine them into a workshop sprint based on what your project actually needs.
Case study
Persona Hats critique for a B2B software product
A B2B product team ran a critique workshop using three persona hats: Business Leader (values outcomes and cost, needs information fast), IT Manager (values integration speed and security, skeptical until convinced of unique value), and Developer (values speed and ease of use, needs to build a business case for purchasing decisions). Each group wore one hat while doing a cognitive walkthrough of a redesigned dashboard, capturing questions and concerns from their assigned user's perspective.
Why it works: By forcing each group to adopt a specific user perspective — complete with artifacts reminding them of that user's core values — the critique surfaced different issues than a general design review would. The Business Leader group caught information density problems, the IT Manager group found integration concerns, and the Developer group identified documentation gaps. The combined output was richer than any single-perspective review.
Common pitfalls NN/g
Starting with activities instead of goals
The most common planning mistake is picking activities first ("let's do a brainstorm and then dot voting") without defining what the workshop needs to achieve. Use the Workshop Design Canvas: Goals → Questions → Processes. Activities are the last thing you choose, not the first.
Running a workshop that should have been a meeting
Not every collaboration needs a half-day facilitated session. If you're broadcasting information, updating status, or making a decision where one person has authority, a meeting is more efficient. Reserve the workshop format — and the significant preparation it requires — for problems that genuinely need diverse input and co-owned outcomes.
Skipping the post-workshop follow-up
Workshops generate energy and alignment that decays rapidly without documentation and next steps. If participants leave excited but nobody captures the output, assigns actions, or communicates results to absent stakeholders, the workshop was a team-building exercise, not a strategic tool. Budget time for follow-up as part of the workshop design, not as an afterthought.
Letting dominating participants derail the process
Unaddressed domination — whether from a HIPPO, an enthusiast, or an expert — quietly kills participation from everyone else. Most people won't push back on a dominant voice; they'll just check out. Use structural solutions (silent generation, round robin, quotas) proactively rather than waiting until someone has already taken over.