The Synthesis Workshop: Turning Data into Decisions

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.

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:

Preparation Checklist

Before the workshop:

1. Complete initial analysis — Code your data, identify preliminary patterns
2. Select compelling evidence — Choose 15-25 key quotes/clips that represent major themes
3. Prepare physical materials — Print quotes, prepare boards, gather supplies
4. Brief stakeholders — Share context so they arrive ready to engage
5. 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:

1. Everyone writes sticky notes with their ideas
2. Notes get grouped by "similarity"
3. Groups get labeled with theme names
4. Everyone feels productive
5. 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

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:

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:

1. What is the problem? (Theme description)
2. How severe is it? (Impact on users)
3. How prevalent is it? (How many users affected)
4. What should we do? (Recommendation)
5. Who owns it? (Accountability)

The Severity × Frequency Matrix

Use this framework to prioritize themes:

The Prioritization Exercise

Materials: Theme cards from affinity mapping, large matrix on wall/board

Process:

1. Read each theme aloud
2. Discuss: "How severe is this for affected users?"
3. Discuss: "How many users does this affect?"
4. Place on matrix (facilitator makes final call if disagreement)
5. Repeat for all themes

Rules:

• Use evidence to justify placement
• Disagreements resolved by returning to data
• Facilitator prevents groupthink
• Document reasoning for each placement

For how collaborative synthesis drives strategic influence, see From Data Collector to Strategic Partner.

Workshop Facilitation Guide

Before the Workshop

The Agenda

Ground Rules to Establish

Read these at the start:

1. "We are here to interpret data, not generate ideas."
2. "Every claim must link to evidence. 'I think' is not evidence."
3. "Disagree with interpretations, but accept the data."
4. "The goal is a prioritized action list, not a perfect map."
5. "Silence means consent. Speak now or accept the conclusion."

Facilitation Techniques

Common Failures and Fixes

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.

1. Prepare rigorously: Arrive with 70-80% of analysis complete
2. Enforce evidence: Every sticky note must cite a source
3. Prioritize ruthlessly: Use Severity × Frequency, not voting
4. Assign owners: Insights without accountability are suggestions
5. 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.

For the rigorous analysis that should precede collaborative synthesis, see Qualitative Thematic Analysis: From Codes to Insights.

For how to turn workshop outputs into effective research reports, see Anatomy of an Effective Report.