By the end of this lesson you can
- Analyse qualitative and quantitative test data.
- Find patterns across sessions and identify root causes.
- Turn findings into clear, evidence-based recommendations.
The idea
Analysis turns notes and recordings into findings the team can act on.
Debrief quickly
After each session, spend 10–15 minutes with observers noting the biggest issues while memories are fresh.
Qualitative analysis
Gather observations onto notes, one per observation, tagged with participant and task. Group them by task and by theme, as in affinity mapping. Look for patterns: what happened to several people? Then ask why: what is the root cause? Several symptoms often share one cause.
Quantitative measures
- Task success rate: percentage who completed each task.
- Time on task: useful for comparison, less so with small samples.
- Errors: number and type.
- Ratings: such as a single ease question after each task, or the System Usability Scale (SUS) at the end.
With five participants, report numbers carefully ("4 of 5 participants") rather than as percentages that imply precision.
Findings and recommendations
A finding states what happened and why, with evidence. A recommendation states what to change. Keep them linked.
Why it matters in real projects
Raw observations do not change products; clear findings do. Good analysis distinguishes one-off quirks from real patterns, identifies root causes so fixes work, and presents evidence in a way that persuades.
A realistic example
In a test of a recipe app, four of five participants failed to adjust serving sizes, two tapped the ingredient list, and one said "I'd just do the maths myself."
Grouping observations reveals the root cause: the serving control sat below the fold and looked like static text. The finding reads: "4 of 5 participants could not change servings because the control was not visible or recognisable as interactive." The recommendation: move a visible stepper next to the ingredients heading.
Step by step
Debrief after each session
Note top issues with observers.
Transfer observations
One observation per note, tagged with participant and task.
Group
Cluster by task and theme.
Find root causes
Ask why for each pattern.
Calculate measures
Compute success rates, errors and ratings.
Write findings and recommendations
Link each recommendation to evidence.
Common mistakes
Mistake Over-reacting to one participant.
Instead Look for patterns, but weigh severe one-offs.
Mistake Reporting percentages from five people.
Instead Use counts such as "4 of 5".
Mistake Recommendations without evidence.
Instead Link each to observations.
Check your understanding
Choose an answer, then check it. There is an explanation either way.
Practice exercise
Exercise · about 1 h 15 min
Analyse a test
Analyse notes from a usability test (your own or a sample).
Steps
- Transfer observations onto notes.
- Group and identify patterns.
- Find root causes.
- Write five findings with recommendations.
Deliverable
An analysis board and a findings list.
Self-assessment
Tick each item when it is true of your exercise. Be honest; this is for you.
4 items
Summary
- Debrief quickly, then group observations.
- Find patterns and root causes.
- Use measures carefully with small samples.
- Link findings, evidence and recommendations.
Further reading
Third-party sources, chosen for reliability. They open in a new tab.
Your notes
Marking complete updates your course and roadmap progress.