Usability testing produces a flood of raw material: observation notes, screen and audio recordings, task success and failure records, time-on-task numbers, quotes, and your own impressions. Collecting and organizing test data is the discipline of capturing that material consistently during sessions and then structuring it so that patterns across participants become visible. Without a plan for recording and organizing, findings tend to collapse into anecdotes about whichever participant was most memorable.
This topic covers four practical pieces. Data collection methods address what you capture and how (note-taking templates, recordings, observer roles, consistent prompts and session openings). Affinity diagramming is the technique of writing individual observations on separate notes and clustering them until themes emerge from the bottom up. Usability issue logs give each problem a stable identifier, description, location in the interface, affected participants, and a severity rating. Synthesizing across participants is the step where you count how many people hit the same obstacle and decide what the evidence actually supports.
As you watch the videos below, pay attention to the habits that make later analysis possible: scripting the parts of a session that should be identical for every participant, using a small and explicit set of criteria so severity ratings stay consistent, and describing findings in terms that match the strength of the underlying data. These are the same habits that will let you defend your redesign priorities in this course's project work.
A short demonstration from Nielsen Norman Group showing how a facilitator introduces a participant at the start of a usability test session, including the use of a facilitator's script. The description points to covering standard opening elements such as explaining the purpose of the session, setting expectations, and working through the script so nothing is forgotten. Expect to see the interaction modeled rather than only described.
Consistent data starts with consistent sessions, and this clip makes the case for scripting the opening so every participant receives the same framing, which is a prerequisite for comparing results across participants.
This video explains how to assign severity ratings to design issues found through usability studies or heuristic evaluation, using a small set of criteria rather than ad hoc judgment. It is likely to discuss factors such as how many users are affected, how much the problem impedes task completion, and whether the issue is persistent. The focus is on reporting findings in a way that distinguishes major problems from minor ones.
Severity rating is the core of a usable issue log, and a short criteria-based approach from NNgroup gives students a defensible, repeatable way to record and rank issues rather than relying on gut feeling.
A brief treatment of how to present UX research results to stakeholders truthfully and responsibly. Based on its description, it addresses representing data honestly, avoiding overstating what a small study can support, and being careful with how numbers and claims from qualitative work are framed. It connects the analysis stage to the communication stage of a project.
It reinforces the synthesis subtopic by showing how aggregated findings should and should not be characterized once you move from raw notes to claims about users.
Together these videos trace the path from session to decision that this module asks you to walk. The facilitation demonstration supports MO1 by showing how standardized sessions yield comparable data in which recurring patterns and pain points can actually be detected rather than confused with facilitator variation. The severity prioritization video maps directly onto MO2, supplying explicit criteria for weighing frequency, severity, and user impact when ranking which issues to fix first. The responsible reporting video supports MO3 by modeling how to state findings accurately, which is exactly the kind of evidence-based rationale you are expected to document alongside each iterative design change.
These videos were chosen from YouTube on October 3, 2026. Each has captions; the player turns them on. Videos on YouTube can be changed or removed — if one no longer plays, tell your instructor. If a player does not appear, use its Watch on YouTube link.