← Back to guides

Reading qualitative data without drowning in it

IntermediateMarch 14, 2026

A method for getting from 30 interview transcripts to three product decisions in a single afternoon.

Synthesis is where research goes to die. You have thirty transcripts, a highlighter, and the afternoon. Four hours later you have a color-coded document, forty tags, and no decisions. Three days later you're still tagging.

The fix isn't a better tool. It's a shorter path.

Read first, tag second

The single biggest time-sink in qualitative synthesis is tagging while reading the first transcript. Whatever theme you see in transcript one becomes the lens through which you read transcripts two through thirty. You'll find that theme everywhere because you're primed to.

Read three transcripts with no tagging at all. Write a paragraph of gut-feel impressions. Only then start tagging. You'll start from a wider frame, and your tag list will cover what's actually there instead of anchoring on the first interview.

Build your tag list as you go

Start with five or six tags, not twenty. Add new ones only when an existing tag genuinely doesn't fit the thing you're reading — not when it sort-of fits but something in the phrasing feels different.

The impulse to create fine-grained tags is a form of procrastination. Fewer, broader tags make patterns visible. More, narrower tags make the document look organized while telling you nothing.

The frequency trap

"The thing most people mentioned is the most important thing." This sounds obvious. It's often wrong.

Some topics are common because they're top of mind (the last thing they used, the last bug they hit). Others are rare because they're embarrassing, or because only power users encounter them, or because they're so fundamental nobody thought to mention them. Frequency correlates with importance loosely at best.

Look at intensity as well as frequency. A theme mentioned by six of thirty people, each time with real frustration, often matters more than one mentioned by twenty people in passing.

Writing the summary first

Before you finish reading, force yourself to write three bullets: "If I had to give a recommendation based on what I've seen so far, here's what it would be." Two minutes, three bullets, no qualifications.

This feels premature. It is premature. The value is that it reveals what you actually think the data is saying, before the remaining transcripts let you keep deferring the conclusion. You'll either refine the bullets as you finish reading, or you'll realize the bullets are wrong and you needed to stop and reconsider. Both outcomes beat "I'll synthesize after I've read everything," which is how afternoons become weeks.

When to use AI

Past forty sessions, volume outpaces what one afternoon can hold. This is where AI-assisted extraction genuinely helps — automated theme identification across all transcripts, then human review of the extracted themes.

The important sanity check: AI will find themes that are statistically present but substantively trivial, and miss themes that are substantively important but mentioned rarely. Treat AI output as a first-pass summary you verify, not as the synthesis itself. The human still has to read a representative sample and confirm the AI read the room right.

The takeaway

The method is tool-agnostic. Highlighter and notebook, Dovetail, Honne, or a plain spreadsheet — any of them work. The shortcut isn't software; it's the discipline of writing an opinion early, keeping your tag list small, and treating frequency as only one signal among several.