A research synthesis wall for turning scattered qualitative signals into product decisions.
- Year
- 2026
- Focus
- Research signals into decisions
- Role
- Product design, research synthesis, information architecture, facilitation
- Themes
- Research synthesis, Decision support, Collaboration, Product discovery
How can a team turn scattered observations into a decision everyone can inspect?
Case specimen
Research signals into decisions
- Messy inputs
- Interview notes · Support themes · Workshop signals · Open questions
- Working frame
- Group signals by decision relevance, confidence, and unresolved assumptions instead of by source alone.
- Decision enabled
- Choose which opportunities are ready to move forward, which need more evidence, and which should be parked.
- What changed
- The concept made research synthesis feel like an active decision tool rather than a static archive.
The situation
Context
Research work often produces more material than a team can use. The opportunity was to design a surface where evidence, ambiguity, and decisions could stay connected.
Problem
Teams needed a way to see patterns across many inputs without flattening nuance or losing the reasoning behind a recommendation.
The work
My role
I shaped the synthesis model, defined the signal taxonomy, designed the wall structure, and prototyped ways to move from evidence to product action.
What made it hard
The hard part was avoiding false certainty. A synthesis wall can make weak signals look more definitive than they are if confidence and gaps are not visible.
Process
I mapped the path from raw notes to clustered themes, then into evidence strength, open questions, product bets, and decisions that could be reviewed by the team.
Key design decisions
Key decisions included separating observations from interpretations, making confidence explicit, and giving every theme a clear next action or unresolved question.
What it changed
Outcome
The project created a clearer format for collaborative synthesis and helped frame research as a living input to product judgement.
What I learned
Synthesis tools should not only organise information. They should preserve the argument behind a product decision.
What I would do differently
I would test the model with a live research project and compare how different confidence labels affect team alignment.