Summary
A synthesis workshop is a sense-making session, not a brainstorming session. The facilitator must bring prepared data (tagged clips, quotes, metrics) for the team to connect—not invent. Every grouping must link to specific evidence; if you cannot cite the source, remove the sticky note. The output is not a 'map' but a prioritized action list using the Severity × Frequency matrix.
A research report written in isolation sits on a shelf. A synthesis workshop that involves the team creates ownership—and ownership drives action.
But most workshops fail. They devolve into brainstorming sessions where opinions masquerade as insights. This guide shows you how to run a workshop that actually works.
The "No Brainstorming" Rule
Let's be clear about what a synthesis workshop is not.
| What It Is NOT | What It IS |
|---|---|
| Brainstorming session | Sense-making session |
| Idea generation | Pattern recognition |
| Creative exercise | Analytical exercise |
| Opinion gathering | Evidence interpretation |
| Democratic voting on preferences | Structured prioritization of findings |
The Critical Input: Prepared Data
You must arrive with prepared data. Without it, you are just hosting an expensive meeting where people share opinions.
What to bring:
| Material | Format | Purpose |
|---|---|---|
| Tagged video clips | 30-90 second segments | Show, don't tell |
| Key quotes | Verbatim on cards/stickies | Direct user voice |
| Quantitative data | Charts, metrics | Scale and severity |
| Observation summaries | Bullet points | Context and patterns |
| Pre-identified themes | Draft categories | Starting framework |
Preparation Checklist
Before the workshop:
- Complete initial analysis — Code your data, identify preliminary patterns
- Select compelling evidence — Choose 15-25 key quotes/clips that represent major themes
- Prepare physical materials — Print quotes, prepare boards, gather supplies
- Brief stakeholders — Share context so they arrive ready to engage
- Set expectations — This is interpretation, not ideation
The "Affinity Mapping" Trap
Affinity mapping—grouping sticky notes by theme—is a powerful technique. It is also routinely abused.
The Problem
In a typical workshop:
- Everyone writes sticky notes with their ideas
- Notes get grouped by "similarity"
- Groups get labeled with theme names
- Everyone feels productive
- Nothing is actually grounded in evidence
The result: a wall of opinions organized into categories. It looks like research output but contains no research.
The Rule
Every group on the board must link back to a specific piece of evidence—a quote, an observation, a metric. If you cannot cite the source, take the sticky note down.
Evidence-Based Affinity Mapping
Step 1: Start with Evidence
Instead of asking "What do you think users struggle with?", start with prepared evidence:
Step 2: Group by Meaning
Physically move evidence cards/stickies into clusters. Ask:
- "These three quotes seem related—what connects them?"
- "Is this the same issue or a different one?"
- "Where does this outlier belong?"
Step 3: Name the Groups
Only after grouping, create theme labels. The label should:
- Describe the pattern, not just the topic
- Be specific enough to be actionable
- Connect to user language where possible
| Weak Label | Strong Label |
|---|---|
| "Navigation" | "Users cannot find settings after initial setup" |
| "Pricing concerns" | "Users fear hidden costs will appear at checkout" |
| "Mobile issues" | "Touch targets too small for one-handed use" |
Step 4: Validate Against Evidence
For each group, verify:
- Does every sticky note belong here?
- Is there enough evidence to support this theme?
- Are we interpreting the evidence or adding assumptions?
The Facilitator's Job
As facilitator, your role is to:
| Do This | Not This |
|---|---|
| Redirect to evidence | Let opinions dominate |
| Ask "What did users say?" | Ask "What do you think?" |
| Remove unsupported notes | Let everything stay up |
| Challenge groupings | Accept consensus without scrutiny |
| Maintain focus on data | Allow tangents into solutions |
The Output: Prioritized Actions
The goal of a synthesis workshop is not a "map" or a "wall of themes." The goal is a prioritized list of actions the team commits to take.
From Themes to Actions
After grouping evidence into themes, the workshop must answer:
- What is the problem? (Theme description)
- How severe is it? (Impact on users)
- How prevalent is it? (How many users affected)
- What should we do? (Recommendation)
- Who owns it? (Accountability)
The Severity × Frequency Matrix
Use this framework to prioritize themes:
| Priority | Criteria | Action |
|---|---|---|
| Critical | High Severity + High Frequency | Address immediately |
| Quick Win | Low Severity + High Frequency | Low effort, high visibility |
| Urgent | High Severity + Low Frequency | Cannot ignore (e.g., data loss) |
| Backlog | Low Severity + Low Frequency | Deprioritize |
The Prioritization Exercise
Materials: Theme cards from affinity mapping, large matrix on wall/board
Process:
- Read each theme aloud
- Discuss: "How severe is this for affected users?"
- Discuss: "How many users does this affect?"
- Place on matrix (facilitator makes final call if disagreement)
- Repeat for all themes
Rules:
- Use evidence to justify placement
- Disagreements resolved by returning to data
- Facilitator prevents groupthink
- Document reasoning for each placement
Workshop Facilitation Guide
Before the Workshop
| Task | Timeline | Owner |
|---|---|---|
| Complete initial analysis | 3-5 days before | Researcher |
| Prepare evidence materials | 2 days before | Researcher |
| Book room, gather supplies | 2 days before | Researcher |
| Send pre-read to attendees | 1 day before | Researcher |
| Confirm attendance | 1 day before | Researcher |
The Agenda
| Time | Activity | Purpose |
|---|---|---|
| 0:00-0:10 | Welcome and ground rules | Set expectations |
| 0:10-0:30 | Context and key findings overview | Orient the team |
| 0:30-1:00 | Evidence review (video clips, quotes) | Ground in user reality |
| 1:00-1:30 | Affinity mapping exercise | Group evidence into themes |
| 1:30-1:45 | Break | — |
| 1:45-2:15 | Theme naming and validation | Ensure evidence-based labels |
| 2:15-2:45 | Prioritization exercise | Severity × Frequency matrix |
| 2:45-3:00 | Action items and owners | Commit to next steps |
Ground Rules to Establish
Read these at the start:
- "We are here to interpret data, not generate ideas."
- "Every claim must link to evidence. 'I think' is not evidence."
- "Disagree with interpretations, but accept the data."
- "The goal is a prioritized action list, not a perfect map."
- "Silence means consent. Speak now or accept the conclusion."
Facilitation Techniques
| Situation | Technique |
|---|---|
| Discussion going off-track | "Let's return to the evidence. What did we actually observe?" |
| One person dominating | "I want to hear from someone who hasn't spoken yet." |
| Opinions stated as facts | "Which participant said that? Can you point to the quote?" |
| Stuck on a grouping | "Let's move on and return to this. We might see it more clearly later." |
| Premature solutioning | "We're prioritizing problems now. Solutions come next." |
| Consensus too easy | "Devil's advocate: what if this isn't as important as we think?" |
Common Failures and Fixes
| Failure | Cause | Fix |
|---|---|---|
| Workshop feels unproductive | No prepared data | Never workshop without evidence |
| Output is a wall of opinions | Allowed brainstorming | Enforce "cite your source" rule |
| Beautiful map, no action | Skipped prioritization | Always end with Severity × Frequency |
| Team does not commit | No assigned owners | Every action needs a name and deadline |
| Findings ignored after | No follow-up | Schedule check-in 2 weeks later |
The Deliverable
After the workshop, produce a concise document:
SYNTHESIS WORKSHOP OUTPUT
Date: [Date]
Attendees: [Names]
Research: [Study name/date]
PRIORITIZED FINDINGS
CRITICAL (Fix First)
1. [Theme] — [Evidence summary] — Owner: [Name] — Due: [Date]
2. [Theme] — [Evidence summary] — Owner: [Name] — Due: [Date]
QUICK WINS
3. [Theme] — [Evidence summary] — Owner: [Name] — Due: [Date]
URGENT (Edge Cases)
4. [Theme] — [Evidence summary] — Owner: [Name] — Due: [Date]
BACKLOG
5. [Theme] — [Evidence summary]
6. [Theme] — [Evidence summary]
NEXT STEPS
- [ ] [Action] — [Owner] — [Date]
- [ ] Follow-up meeting scheduled: [Date]
What This Means for Practice
A synthesis workshop is not a substitute for analysis—it is a mechanism for turning analysis into action.
- Prepare rigorously: Arrive with 70-80% of analysis complete
- Enforce evidence: Every sticky note must cite a source
- Prioritize ruthlessly: Use Severity × Frequency, not voting
- Assign owners: Insights without accountability are suggestions
- Follow up: Schedule the check-in before the workshop ends
The goal is not to make the team feel included. The goal is to make the team responsible for acting on what you learned.