Guide7 min read
How to synthesise twenty interviews in a week
A day-by-day plan for turning a stack of recordings into themes your team will actually read — without pulling all-nighters.
Ines AchterbergResearch Operations ·
Twenty interviews is roughly fifteen hours of conversation. Watch them back to back and you will remember the last three and the one that made you laugh. Synthesis is the work of making sure the other sixteen count too — and it goes faster when you split it into small, deliberate passes rather than one heroic weekend.
Before Monday: agree what you are listening for
Write down the two or three decisions this research is meant to inform. If the study is about onboarding, the decision might be “which setup step do we rebuild first?”. Every highlight you make should help answer one of these questions. Anything else goes in a parking-lot tag so it is not lost, but it does not steal your week.
The five-day plan
| Day | Focus | Output |
|---|---|---|
| Monday | Read transcripts 1–7, highlight only | ≈ 60 highlights, loosely tagged |
| Tuesday | Read transcripts 8–20, highlight only | ≈ 120 more highlights |
| Wednesday | Clean tags, merge duplicates | A tag list under 25 items |
| Thursday | Cluster into themes with a partner | 5–8 named themes with counts |
| Friday | Write insights, pick clips, share | A short report and a 15-minute readout |
Highlight first, interpret later
On the first two days, resist naming themes. Mark what people said and what they did, tag it with something descriptive, and move on. Interpreting too early makes you see the pattern you expected and skip the quote that contradicts it.
“A highlight should still make sense to someone who never watched the call. If it needs your memory to explain it, add a note.”
Cluster with someone who wasn’t in the room
Thursday works best with a partner — a designer, an engineer, a PM. Read highlights aloud and group them. Your partner will ask “is that really the same thing?” at exactly the moments you are tempted to merge two different problems into one tidy theme.
- Name themes as findings, not topics: “Import breaks on real-world spreadsheets”, not “Import”.
- Record how many people raised each theme, not just how many highlights it has.
- Keep one theme for surprises. It is often the most useful slide in the readout.
Friday: share less, link more
A good readout fits on one screen: the decisions you set out to inform, the themes that bear on each one, and two clips per theme. Link everything else. People who want the detail will click through; people who don’t will still leave knowing what customers said.
In Parley
Tag counts and participant counts update as you highlight, so Thursday’s clustering starts from a ranked list rather than a blank board.
Parley, its authors and the companies mentioned here are fictional. This article is demo content for the template and can be replaced with your own.