Turning what you saw and heard into things a team can act on. The discipline is keeping three things apart: what happened, what you think it means, and what to do about it.
Written as practical advice. Where a step rests on established research practice, the source is listed under References. Nothing here is a universal rule.
Exactly what was seen or heard, not what it means. Verbatim quotes and observed behaviour.
Move notes until groups emerge. Do not start from categories you already had.
With a sentence that says what the notes share, not a one-word topic.
What the group of observations tells you. Check it against the notes behind it.
How many participants, how consistent, and what would change your mind.
What it means for the product, before any specific solution.
Only now. Keep it separate so it can be argued with without disputing the finding.
Weak
Users can't find export.
Better
Observation: 4 of 6 participants looked for export in the toolbar before opening Settings.
Why. A count and a behaviour can be checked. A verdict cannot.
Weak
Move export to the toolbar.
Better
Interpretation: the export action may not be visible enough where people expect it.
Why. The interpretation leaves room for more than one fix.
Weak
Export is confusing.
Better
Insight: people need export at the point where they finish reviewing data, not in a separate settings area.
Why. An insight says what people need and when.
Senior designer note“Take notes on what happened, not only what you think it means.”
References