UX Research · Labs · 3 min read
Synthesise a study
A guided lab: take the notes from a small study and turn them into themes, findings and actions on a board, with your team, in one session. Three colours of sticky note, one observation per note, and every finding traced back to the people who said or did it. About two to three hours.
Synthesis is where a pile of notes becomes something a team can act on, and where it most often goes wrong. Done alone, it's one person's opinion with quotes attached. Done with the people who watched the sessions, in a fixed order, it's a shared understanding the team will defend. You'll run that session once, start to finish.
What you'll do:
- Turn session notes into one observation per note
- Sort them into groups with your team, and name the groups
- Write findings on a second colour, and actions on a third
- Trace every finding back to the participants behind it
- Leave with a board someone else can read
You'll need: notes or recordings from at least three sessions (from Run three interviews, or any small study), sticky notes in three colours or a whiteboard tool, one to four colleagues who watched at least one session, about two to three hours.
1. Plan the session
Book it as soon as possible after the last session; GOV.UK's guidance is to analyse while it's "still fresh in people's minds", and to plan about one hour of analysis for every two hours of research (GOV.UK Service Manual, Analyse a research session). Invite everyone who watched: more people lower the risk of one person's bias, and nobody's view of the study gets to dominate. Put the research questions at the top of the board.
2. One observation per note
Each person goes through their own notes and writes one observation per note, on the first colour: something seen or heard, not an interpretation. "P3 redid the split by hand to check it" is an observation. "P3 doesn't trust the app" is an interpretation; it comes later. Put the participant code and the timestamp on every note. NN/g suggests giving people a fixed window for this, usually 5 to 10 minutes depending on how much data there is (Rachel Krause and Kara Pernice, NN/g, 2024).
3. Sort, silently first
Put all the notes up. Everyone moves notes into groups that feel related, including other people's notes, without talking for the first ten minutes. Then talk: name each group with a short sentence, not a single word, split groups that are too big, and park notes that don't fit anywhere in a corner. Don't throw them away: a lonely note can be the one that matters. See From notes to themes, affinity mapping and, for a more careful method, Thematic analysis.
4. Findings, then actions
People check a split before they trust it
Redid a split by hand to check itP3 · 14:40
Scrolled the chat for the photo of the bill, then used the calculatorP4 · 23:15
Asks flatmates to reply "ok" in the chat before payingP6 · 08:10
People check how a split was worked out before they trust it5 of 8 participants
Show the working under every split; test it in round 2
One person carries the admin
Keeps a spreadsheet "because nobody else will"P1 · 12:18
Pays every bill first and chases the others laterP1 · 15:02
"I end up chasing everyone"P6 · 40:02
One person becomes the household's banker, and carries the cost4 of 8 participants
New research question: what would make the banker's job lighter?
Moving out is when it breaks
Left a previous app after a flatmate moved outP3 · 27:15
Still owed part of a deposit, months laterP8 · 18:30
Balances break when someone moves in or out3 of 8 participants: a signal, check in round 2
Add a move-in and move-out question to the next guide
- Observation: seen or heard, with code and time
- Finding: what we learned, with a count
- Action: what we'll do
- Parked: P2 "it evens out" (04:55), kept for round 2
On the second colour, write each group's finding as a short statement of what you learned, and stick it on the group. On the third colour, write actions: a design idea, a new research question, a change to the prototype, a backlog item (GOV.UK Service Manual). Then prioritise: which findings answer the research questions, and which change what the team does next?
5. Trace every finding
Before anyone leaves, go through each finding and count the participants behind it: which codes are on the notes under it? Write the count on the finding ("5 of 8"). This course's rule of thumb: if a finding rests on one person, call it a signal, not a finding, and say so. Then take a photo or export of the board, and write the findings up as headlines for Present findings in ten minutes.
6. Check your work
Reflection questions: Which group did you and your colleagues disagree about, and what did the notes say? Which finding surprised you, given what you expected before the study?
Related
From notes to themes, affinity mapping · Thematic analysis · Writing insights that change decisions · AI-assisted synthesis, step by step