Module 11 of 12 · 15 min read
Workshop Techniques: The UX Lead's Facilitation Toolkit
Design and run workshops that reach a decision: fundamentals, a planning canvas, techniques by purpose, six ready-to-run agendas, remote tips and how to handle difficult dynamics.
Why it matters
As a lead, your main tool shifts from the design file to the room: aligning stakeholders, co-creating standards with designers, prioritising demand across teams, building a shared vision. You may already have run a training session or a design sprint; this module turns that into a broad facilitation repertoire.
Workshops also suit leads who are not the loudest person in the room. A good facilitator doesn't need to be the loudest voice. They design a structure in which everyone's voice counts. That is the same structure you need to lead a distributed team that works across several products.
Common pitfalls for new leads:
- A workshop with no outcome. People leave with a nice board and nothing decided, and they trust your next invitation less.
- Facilitating and arguing at the same time. You push your own view while you're supposed to guide the process.
- Mixing generating and judging. Ideas get shot down before they're fully out.
- No follow-up. The summary never arrives, and the decisions slowly dissolve.
1. Facilitation fundamentals
1.1 The facilitator's job
- Own the process, not the content. You guide how the group thinks, not what it concludes.
- Protect the goal, the time, and the quiet people.
- Make thinking visible: on walls, boards, sticky notes.
- Get to a decision or a clear next step. A workshop without an outcome erodes trust in future workshops.
Facilitator vs participant hat: as UX lead you're often both. If you have strong content opinions, get a co-facilitator, or say explicitly when you switch: "Taking off my facilitator hat for a moment, here's my view as UX lead…"
1.2 Diverge → Converge (the "double diamond" of every session)
| Phase | What happens | Mode |
|---|---|---|
| 1. Problem framing | Agree what you're solving and why | Start |
| 2. Open up (generate) | Many ideas, no judgement | Diverge |
| 3. Emergent zone ("groan zone") | Confusion, overlap, competing ideas | The messy middle |
| 4. Narrow down (choose) | Cluster, prioritise, decide | Converge |
| 5. Decision & actions | Owners, dates, next steps | Commit |
Every agenda alternates between diverging (many ideas, no judgement) and converging (cluster, prioritise, decide). Most bad workshops mix the two. People judge ideas while they're still generating them.
Sam Kaner calls the uncomfortable middle the "groan zone". Confusion there is normal, so don't rush out of it.
1.3 Golden rules
- Silent individual work before group discussion ("1-2-4-All" logic). It removes the loudest-voice bias and the HiPPO effect (the highest-paid person's opinion).
- Timebox everything and show a visible timer.
- One conversation at a time.
- Separate generating from evaluating.
- Decide how you'll decide before you start: vote, consent, approver (DACI)?
- Capture outputs live. Send a summary within 24 hours.
2. Designing a workshop: the canvas
Fill this before every workshop. If you can't fill in Outcome, you don't need a workshop. You need a meeting or an email.
WORKSHOP CANVAS
Title:
Why now (the problem behind the workshop):
Outcome (the tangible output: decision / prioritised list / map / principles):
Participants (who + why each one; max 8–10 per facilitator):
Decision method (vote / consent / approver = ___):
Pre-work (what participants read/do beforehand):
Agenda (activity — purpose — diverge/converge — minutes):
Materials (Miro/FigJam board, templates, data, user quotes):
Risks (dominant person? politics? missing decision maker?) & mitigations:
Follow-up (who sends summary, by when, where is it stored):
Agenda skeleton (2 hours)
| Time | Block | Mode |
|---|---|---|
| 0:00 | Welcome, goal, agenda, roles, "how we'll decide" | — |
| 0:10 | Warm-up / check-in tied to topic | Connect |
| 0:20 | Context: data, user evidence, constraints | Inform |
| 0:35 | Generate (silent, then share) | Diverge |
| 1:05 | Break | — |
| 1:15 | Cluster & make sense | Converge |
| 1:35 | Prioritise / decide | Converge |
| 1:50 | Actions, owners, dates; check-out | Commit |
3. Techniques by purpose
A. Opening & connecting
| Technique | How | Time | When |
|---|---|---|---|
| Check-in question | Each person answers one question in a sentence ("One word for how UX feels in your team today") | 5–10 min | Every session; sets tone, surfaces mood |
| Expectations & concerns | Silent sticky notes: "I hope… / I worry…" | 10 min | High-stakes or political sessions |
| Impromptu Networking (Liberating Structures) | 3 rounds of pair conversations on a question, 4 min each | 15 min | Kick-offs with people from different teams |
| Working agreements | Group agrees 3–5 norms ("cameras on", "challenge ideas, not people") | 10 min | Recurring groups (critique, design-system council) |
B. Understanding the problem / discovery
| Technique | How | Time | When |
|---|---|---|---|
| Affinity mapping | Write findings/quotes on stickies → cluster silently → name clusters | 30–45 min | Synthesising research, user interviews, feedback |
| Empathy map | Says / Thinks / Does / Feels for a user role | 20–30 min | Aligning stakeholders on who the user is |
| Journey / service blueprint mapping | Map stages, actions, pain points, systems, back-office | 60–90 min | Processes that cross teams (e.g., a booking process that spans several apps) |
| Problem tree | Core problem in the middle; causes below, effects above | 30 min | Moving from symptoms to root causes |
| 5 Whys | Ask "why?" repeatedly about one problem | 15 min | Quick root-cause on a specific issue |
| Assumption mapping | Plot assumptions on Known↔Unknown × Important↔Unimportant; test the "important & unknown" ones | 30–45 min | Before investing in a solution; turning opinions into research questions |
| Stakeholder mapping | Power × interest grid together with the team | 30 min | Start of any initiative (see module 10) |
C. Framing & ideation
| Technique | How | Time | When |
|---|---|---|---|
| How Might We (HMW) | Turn pain points into "How might we…?" questions; vote on the best | 20 min | Bridge from problems to ideas |
| Crazy 8s | Fold paper into 8, sketch 8 ideas in 8 minutes | 10 min | Fast divergence, gets non-designers sketching |
| Brainwriting (6-3-5) | 6 people × 3 ideas × 5 rounds; pass sheets and build on others' ideas | 30 min | Generating many ideas without dominant voices |
| Round-robin sketching | Sketch → pass → critique/improve → pass | 20–30 min | Building collective ownership of a solution |
| Worst possible idea | Brainstorm terrible ideas, then invert them | 15 min | Unblocks stuck or anxious groups |
| Analogous inspiration | "How does an airport/hospital handle exceptions?" | 20 min | Fresh thinking on complex operational problems |
D. Prioritising & deciding
| Technique | How | Time | When |
|---|---|---|---|
| Dot voting | Each person gets 3–5 dots and votes silently (avoid group-think by revealing together) | 10 min | Fast narrowing |
| Impact × Effort 2×2 | Place items; pick "high impact / low effort" first | 20–30 min | Quick wins, roadmap seeds |
| MoSCoW | Must / Should / Could / Won't | 30 min | Scoping a release or initiative |
| Weighted scoring | Agree criteria + weights, then score (see module 07) | 45–60 min | Allocating UX capacity across teams; politically sensitive choices |
| Buy a Feature | Give participants a budget to "buy" items | 30 min | Making trade-offs tangible for stakeholders |
| Fist to Five | Show 0–5 fingers for support; discuss anything ≤ 2 | 5 min | Quick consensus check |
| Consent decision (Sociocracy) | "Is this good enough for now and safe enough to try? Any objections?" | 10–20 min | Standards and process changes; avoids endless consensus |
| DACI | Name Driver, Approver, Contributors, Informed before discussing | 10 min | Any decision that crosses teams |
E. Alignment & vision
| Technique | How | Time | When |
|---|---|---|---|
| Future headline / Cover Story | "It's three years from now and an article praises UX in our organisation. What does it say?" | 30–45 min | Co-creating a UX vision (module 06) |
| Remember the Future | Imagine success happened; describe what made it happen | 30 min | Vision + identifying enablers |
| Principles workshop | Generate candidate principles → test with the "opposite test" → apply to real past decisions | 60–90 min | Design principles (module 06) |
| Rose / Thorn / Bud | What's working / painful / promising | 20–30 min | Current-state assessment; first 30 days |
| Start / Stop / Continue | Three columns | 20 min | Practice reviews, team kick-off |
| Sailboat | Wind (helps), anchors (holds back), rocks (risks), island (goal) | 30–45 min | Team or programme reflection |
F. Retrospectives & team health
| Technique | How | Time | When |
|---|---|---|---|
| Classic retro | What went well / what didn't / what we'll try | 45 min | After a project or quarter |
| 4Ls | Liked / Learned / Lacked / Longed for | 45 min | Learning-focused retro |
| Lean Coffee | Participants propose topics, vote, discuss in timeboxes | 45–60 min | UX guild, open community sessions |
| Team health check | Anonymous 1–5 scores on health dimensions → discuss lowest (module 04) | 45 min | Quarterly |
| Timeline retro | Draw the project timeline; mark highs and lows | 45–60 min | Long initiatives (e.g., a migration) |
G. Liberating Structures (favourites for a UX lead)
A free, open collection of 33 micro-structures for inclusive meetings. Learn these five first:
| Structure | What it does |
|---|---|
| 1-2-4-All | Think alone → pairs → foursomes → whole group. The default for equal participation |
| TRIZ | "What could we do to guarantee the worst outcome?" → then stop doing those things |
| 15% Solutions | "What can you do now, with your own discretion and resources?" Ends workshops with action |
| Troika Consulting | One person presents a challenge; two others consult while the presenter turns away and listens. Good for peer coaching between designers |
| What, So What, Now What? | Facts → meaning → action. Good for debriefing research or a pilot |
4. Ready-to-run agendas for a UX lead
The agendas below assume a typical setting: a UX team of designers spread across several product teams, each working with its own product manager and developers. Adjust the times and the names of groups to your organisation.
4.1 UX Listening Workshop (first 30 days) — 90 min, designers only
Outcome: a shared picture of the current state + top pain points.
- Check-in: "One word for UX in your team" (5)
- Rose / Thorn / Bud on: tools, process, collaboration with product managers and developers, growth (25)
- Affinity mapping of thorns (20)
- Dot vote: top 3 problems (10)
- 15% Solutions on the top problem (20)
- Check-out: "What do you want from a UX lead?" (10)
4.2 Cross-team Design Critique — 60 min, every two weeks
Outcome: better work, shared patterns, connected designers.
- Presenter: context, goal, stage, what feedback I want (5)
- Silent review: questions and observations on stickies (5)
- Clarifying questions only (10)
- Feedback against goals/principles: "I like / I wish / What if" (20)
- Presenter summarises takeaways (5)
- Second presenter (or pattern spotting: "Have other teams solved this?") (15)
4.3 Design-System Standard Workshop — 2 h, designers + frontend developers
Outcome: one agreed standard (e.g., data table filtering).
- Context: screenshots of current variants across apps (10)
- Use-case inventory per team (silent, then share) (20)
- Affinity: common vs team-specific needs (20)
- Break (10)
- Crazy 8s / round-robin sketching of the shared pattern (25)
- Converge: pick direction with dot vote, then consent decision (20)
- DACI for building it; tier (core vs recommended) (15)
4.4 UX Capacity & Priorities Session — 90 min, product leads / product managers
- Goal, ground rules, decision method (Approver named) (10)
- Demand vs capacity visual (10)
- Agree/adjust criteria weights (15)
- Score requests in pairs (pairs from different teams reduce bias) (25)
- Review ranking; discuss surprises (20)
- Allocation proposal + "what we're not doing" + enablement options (10)
4.5 UX Vision Co-creation — half day, designers + selected stakeholders
Outcome: draft vision themes + principles.
- Check-in + user video/quotes as grounding (20)
- Cover Story (three years from now) in small groups (45)
- Share & affinity-map themes (30)
- Break (15)
- Remember the Future: what enabled it? (30)
- Draft principles + opposite test (40)
- TRIZ: what would kill this vision? (20)
- Next steps: who drafts v1, feedback round (10)
4.6 Project Kick-off with Product Manager & Developers — 90 min
Outcome: shared problem understanding, roles, success metrics.
- Problem statement & users (15)
- Assumption mapping (25)
- Success metrics: Goals → Signals → Metrics (20)
- Roles & DACI; ways of working (15)
- Risks + first research questions (15)
5. Remote & hybrid facilitation (the distributed-team reality)
Tools: Miro, FigJam or Mural for boards; breakout rooms in Teams, Zoom or Meet; Mentimeter, Slido or built-in polls for votes. FigJam has built-in templates, voting and a timer, which helps if your team already lives in Figma.
Rules for remote
- Shorter blocks. Max ~90 min per session; split longer workshops across days.
- Prepare the board fully before the session: frames per activity, instructions on the board, a "parking lot".
- Do a tech check at the start (2 min): everyone adds a sticky with their name to prove they can edit.
- Cameras on for discussion; it's fine to switch off for silent work.
- Assign breakout roles: timekeeper, note-taker, presenter.
- Use async pre-work to save live time for discussion and decisions.
- Hybrid is the hardest. If even one person is remote, have everyone join on their own laptop and board ("remote-first hybrid").
- Timezones & languages. Rotate time slots; use simple English; allow writing first so non-native speakers can formulate ideas.
6. Handling difficult dynamics
| Situation | Move |
|---|---|
| Dominant participant | Switch to silent writing or round-robin. "Thanks, [name]. Let's hear from people we haven't heard yet." Give them a role (timekeeper). |
| Silent participants | Use 1-2-4-All; ask in pairs first; direct but safe invitations ("[name], anything from the finance perspective?") |
| HiPPO / senior stakeholder overriding | Anonymous voting; agree the decision method upfront; pre-meet them before the session. |
| Going off-topic | "Great point. Let's park it" (visible parking lot, revisit at the end). |
| Conflict between two people | Name it neutrally, return to the shared goal, separate interests from positions, and take it offline if personal. |
| Group stuck in the groan zone | Normalise it ("This is the messy middle, it's expected"); narrow the question; take a break. |
| Cynicism ("we tried this before") | Acknowledge, ask what was learned, and use TRIZ or 15% Solutions to make it concrete. |
| Running out of time | Prioritise the decision over completeness. Agree what will be finished async and by whom. |
| Key decision maker absent | Reframe output as a recommendation, or reschedule. Don't fake a decision. |
7. Facilitation for an introverted lead
- Preparation is your superpower. A well-designed agenda does most of the facilitation work.
- Let the structure speak. Clear instructions on the board reduce the need for improvisation.
- Co-facilitate at first, e.g., with your manager or a designer you trust; alternate roles.
- Script the transitions ("Now we'll move from generating to choosing…") and the tough moments ("Let's hear from someone new").
- Use silence deliberately. Wait 7 seconds after a question. Someone will fill it.
- Energy management. Block 15–30 min after a big workshop to recharge and write the summary.
8. Practice
Build your facilitation skill step by step, from low risk to high stakes:
| Step | Exercise | Output |
|---|---|---|
| 1 | Use 1-2-4-All in a normal team meeting | Note how participation changed |
| 2 | Run a Rose/Thorn/Bud retro with your team (45 min) | Summary + 2 actions |
| 3 | Facilitate a cross-team critique (agenda 4.2) | Recurring ritual |
| 4 | Run a design-standard workshop (agenda 4.3) on a real pattern | Agreed standard |
| 5 | Facilitate a session with product managers/stakeholders (kick-off or prioritisation) | Decision + DACI |
| 6 | Design and run a half-day vision workshop | Vision draft |
| 7 | Ask 2 participants for feedback on your facilitation after each session | Facilitation log |
Post-workshop self-review (5 min)
Did we reach the outcome? (yes / partly / no — why)
Who spoke most / least? What would I change?
Which activity worked best / worst?
Timing: where did I over/underestimate?
One thing to try next time:
Workshop summary template (send within 24h)
Subject: [Workshop] — outcomes & next steps
Goal:
Participants:
Key outcomes / decisions:
1.
Actions (owner — due date):
-
Parked topics:
Board link / photos:
Next session (if any):
Evidence to collect
Keep proof in your leadership log (see 12-Month Learning Plan):
- One workshop canvas, its agenda and the summary you sent afterwards.
- A decision that was reached in a workshop and actually held.
- Feedback from participants on your facilitation, and what you changed because of it.
Talking about it
Workshops are visible leadership, so people will ask about them. When you describe one to your manager, a stakeholder, or in a promotion or hiring conversation, talk about the outcome and the design, not the sticky notes:
- "The goal was to agree one filtering pattern across four products. I chose silent inventory first so every team's needs were on the table, then a consent decision so we didn't get stuck chasing full consensus."
- "The hardest moment was a senior stakeholder pushing their option. Because we'd agreed the decision method upfront and voted anonymously, the group could choose on evidence."
- "Afterwards the summary went out within 24 hours, and the pattern was in the design system the next quarter."
9. Read / watch
See Library → Facilitation & workshops. Key sources:
- Liberating Structures: https://www.liberatingstructures.com/ (free, all 33 structures)
- Atlassian Team Playbook: https://www.atlassian.com/team-playbook (free plays: DACI, retros, kick-offs)
- Gamestorming by Dave Gray, Sunni Brown & James Macanufo (2010). The classic catalogue of workshop games.
- Facilitator's Guide to Participatory Decision-Making by Sam Kaner. Diverge/converge and the groan zone.
- Sprint by Jake Knapp (2016). The design sprint, plus many reusable exercises (Crazy 8s, HMW, decision-making).
- The Workshop Survival Guide by Rob Fitzpatrick & Devin Hunt. Short and practical workshop design.
- NN/g articles on UX workshops and facilitation (in the Library).
- Miro / FigJam template galleries for ready-made boards.
Check yourself
Answer out loud, then open the section to compare.
- Why diverge before converging? → answer
- Which technique would you use to prioritise across teams? → answer
- How do you handle a dominating participant? → answer
Connections
← Module 10: Stakeholders, Influence & Change · UX Lead Course · Module 12: AI and the UX Lead →
Related
- Module 10: Stakeholders, Influence & Change: facilitation in the influence context
- Module 4: People Leadership: critique as feedback
- Module 6: UX Strategy & Vision: principles workshop input
- Module 7: DesignOps, Team Models & Capacity: weighted scoring for prioritisation
- Module 3: Personal Leadership Presence: introversion as a strength
- Module 5: Enterprise & Internal Applications: research with internal users