Skill Profile
Research Synthesis
"Clustering fragmented research — interview notes, survey responses, support tickets, and analytics — into patterns, then turning those patterns into a prioritised, agreed set of problems to solve before any design begins."
YOUR SKILLS
Problems This Skill Solves
- A team drowns in research — hundreds of pages of notes — but cannot say what to build next.
- Different stakeholders each remember the one user quote that supports their preferred feature.
- Design starts from opinion because nobody turned the raw research into a shared, prioritised problem list.
- The same usability issue keeps recurring because its root cause was never named and grouped.
Roles That Use This Skill
1 total · 1 industryThis skill is concentrated in one industry.
UX/Product Design / Technology
"Synthesis is just summarising the research."
Summarising restates what was found; synthesis reorganises it into a structure that did not exist in the raw data — patterns, priorities, and a reframed problem. A summary tells you what users said; synthesis tells you what to do about it.
"More data makes synthesis easier."
More data makes synthesis harder, not easier. The skill is deciding what to ignore. Volume without a method to cluster and prioritise produces noise, not direction.
Research & Outlook
AI can cluster and tag qualitative data at speed, but deciding which patterns matter, separating signal from artefact, and reframing the problem remain human judgement calls. The task shifts from manual tagging to directing and auditing machine-clustered themes.
See This Skill In Action
Watch a professional demonstrate Research Synthesis in a real working environment — what it looks like, how it's applied, and why it matters.
Design / Research
Research Synthesis
Also Known As
Growth Path
Groups raw observations into themes and can summarise what the research says.
Separates observation from inference, prioritises problems against user impact, and produces a problem list the team aligns on.
Synthesises conflicting qualitative and quantitative sources under stakeholder pressure and reframes the problem itself when the evidence demands it.
How to Practise
- 1.Take 8 interview transcripts and cluster observations into themes without forcing a conclusion
- 2.Turn one messy research set into a single prioritised problem statement the team can act on
- 3.Practise separating what a user said from what you inferred — tag each observation as fact or interpretation
How to Prove
- ·An affinity map plus the prioritised problem list it produced on a real project
- ·A synthesis readout that visibly changed what the team decided to build
- ·A before/after showing scattered findings reduced to three ranked problems