Many synthesis workshops only summarize findings, without concrete decisions. This can waste time and hinder product advancement. The goal is to convert research observations into clear actions, with defined responsibilities, so the team can inspect potential improvements and direct their work.
Prioritize Observations, Not Hypotheses
Begin the workshop by focusing on direct user observations, not pre-existing assumptions. Group these observations by emergent themes, identifying patterns and anomalies. It's crucial to include negative or contradictory data, as they reveal important nuances. Each group of observations should have its origin clear, allowing traceability of information and validation of its relevance. This approach grounds discussions in concrete evidence.
Structure Discussion for Action
After grouping observations, direct the team to discuss implications and potential solutions. The focus should be on 'what will we do with this?'. For example, imagine that users of a banking app hypothetically report difficulty finding the 'pay bill' option on their phone. The discussion should lead to a decision on improving navigation or the feature's label. Recording dissent allows the team to inspect areas needing further investigation or different perspectives.
Record Clear Decisions and Next Steps
Every decision made must be meticulously documented. For each item, define: the decision itself, the owner (who will be responsible), the supporting evidence (grouped observations), and the next test or validation. Avoid duplicating information already present in research repositories or executive reports. The workshop allows the team to create a clear, concise plan for moving discoveries into action.
For Actionable Synthesis
- Start with direct observations, grouping them by emerging themes.
- Record each decision with owner, evidence, and next test.
- Include negative data and dissent for a complete view.
When planning your next synthesis workshop, structure it so each discussion culminates in a documented decision. Create a simple table with the decision, owner, evidence, and next test. This allows the team to inspect how research can inform product development, generating a concrete artifact.
Your next discovery begins with a question.
Test an idea, observe the experience and bring evidence to your team.
Create my first studyFree · 1 study · 50 responses/month · no card
