Controlled usability testing borrows its logic from experimental science. Before you can say that one interface is "better" than another, you need a plan that specifies what you are changing, what you are measuring, and what you are holding constant. That plan is your experimental design, and it determines whether the numbers and observations you collect actually mean anything.
This topic introduces the vocabulary and decisions behind that plan: independent variables (what you manipulate, such as two versions of a navigation menu), dependent variables (what you measure, such as time-on-task, error counts, or completion rates), and the control of everything else so that differences in results can be traced back to the design and not to noise. You will also look at internal validity (did my manipulation really cause the observed effect?) versus external validity (will this hold up outside my lab?), the difference between formative studies that shape a design in progress and summative studies that evaluate a finished one, and the ethical obligations you owe participants: informed consent, the right to stop, confidentiality, and never making a participant feel that they are the thing being tested.
As you watch the videos below, keep a running list of three things: what was manipulated, what was measured, and what could have gone wrong (a confound, a biased task order, a leading question). Notice also where the videos emphasize structured quantitative comparison versus open-ended qualitative insight. Both are legitimate; the choice depends on the question you are asking and on where you are in the design cycle.
A focused tutorial on the distinction between independent and dependent variables, the foundational vocabulary of any experiment. Expect clear definitions, worked examples of identifying which variable is manipulated and which is measured, and likely discussion of how to phrase a hypothesis around them. The test-prep framing keeps the explanation concrete and example-driven.
This maps directly onto the Independent and Dependent Variables subtopic and gives you the precise language you will need when you write up a usability study plan. Mometrix Academy produces instructional material for exam preparation, so the treatment is deliberately unambiguous and repeatable.
A short roadmap from Nielsen Norman Group laying out six steps for planning a systematic program of A/B tests rather than one-off comparisons. The description points to sequencing decisions, defining what you will vary, and optimizing a design over the long term. A/B testing is the most common applied form of controlled comparison in UX work.
It shows experimental design in its real industry form: one variable changed at a time, an outcome metric chosen in advance, and results used to decide. NNgroup is a leading authority in usability research, and the video fits the summative, measurement-oriented side of the formative-versus-summative distinction.
A longer introduction to qualitative user research, covering how it differs from quantitative approaches and how to get started conducting it. Based on the title and description, it is likely to address planning research questions, recruiting and talking with participants, and gathering the kind of observational and interview data that explains why users behave as they do. It is framed for people new to UX research.
Qualitative methods supply the formative, exploratory half of the study-type decision and the think-aloud style observations that complement your numbers. CareerFoundry produces structured introductory UX training, so this gives useful context on when a controlled experiment is the wrong tool and an open inquiry is the right one.
Together these videos prepare you to run and interpret a controlled session rather than just attend one. The variables tutorial and the A/B testing roadmap give you the design discipline behind MO3: if you know which variable you manipulated and which you measured, you can recognize when an uncontrolled factor such as task order, facilitator prompting, or a participant's prior experience has confounded an observation. The A/B roadmap also reinforces MO2 by treating metrics as things you decide on before testing, which is how completion rates, error counts, and time-on-task become comparable across participants. The qualitative research video supports MO1 and the qualitative half of MO2, modeling the neutral, non-leading way you should guide participants through task scenarios and capture think-aloud commentary without steering their behavior.
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.
Any usability study is only as good as the people who sit down to use the interface. Participant selection and recruitment is the process of deciding who your target users actually are, writing down the criteria that qualify or disqualify someone from your study, finding those people, confirming they really match your criteria, and getting them scheduled into sessions. Get this wrong and even a perfectly run test session produces findings that do not describe your real users.
In this module you will be running controlled test sessions and collecting measurable data, so recruitment directly determines whether that data means anything. A sample drawn from convenient friends and classmates, or from people who misrepresented their experience on a screener, introduces bias that cannot be corrected afterward. Sample size matters too: the number of participants you need depends on whether you are looking for qualitative insight into problems or quantitative estimates of metrics such as task time and completion rate.
As you watch the three videos below, keep a running list of practical decisions you will have to make for your own study: how you would word a screener question so it does not telegraph the "right" answer, which recruiting channel fits your budget and timeline, what you would exclude on, and how many participants your study goal actually justifies. All three come from Nielsen Norman Group, a long-established usability research and consulting firm, so expect practitioner-oriented guidance rather than academic theory.
This video surveys five different channels for finding user research participants, from recruiting agencies and customer lists to intercepting users in context and online panels. Based on the title and description, it frames each option around the central requirement that participants genuinely represent the target audience, and it is likely to touch on the trade-offs in cost, speed, and quality among the methods. Expect concrete tactics you could apply to a student project as well as to industry work.
It maps directly onto the screening and recruitment methods subtopic and gives you more than one option, which is useful when the ideal recruiting channel is out of reach for a course project. NN Group is a well-known source of applied usability guidance, so the advice reflects current professional practice.
This video focuses on screening, the step between identifying candidates and admitting them to your study, and presents best practices for recruiting participants who truly match the target audience. The title signals an emphasis on how poor screening introduces bias, which connects screening questions to the validity of the data you later collect. Expect guidance on how screener wording and candidate self-selection can let the wrong people into a study.
It covers inclusion and exclusion criteria and screening in a single focused five minutes, and it explicitly ties recruitment decisions to bias, which is the reason this topic matters for your data. It pairs naturally with the recruitment-methods video as the quality-control step that follows.
This video addresses sample size and argues that the widely cited figure of five users applies to qualitative usability testing, not to quantitative studies. It explains why the number of participants needed differs between finding usability problems and estimating metrics with reasonable confidence. Expect a clear statement of when the small-N rule of thumb is appropriate and when a larger sample is required.
It targets the sample size subtopic directly and corrects one of the most commonly misapplied rules in usability work, which matters because you will be collecting both qualitative and quantitative data in this module.
Together these videos set up the conditions under which the module outcomes can actually be met. Recruiting and screening representative participants is what makes a facilitated test session (MO1) produce findings about your intended users rather than about whoever was available. The sample size video supports MO2 by clarifying how many participants different kinds of data require, so that task completion rates, error counts, and time-on-task are gathered from an appropriate number of people, while think-aloud observations can come from a smaller qualitative sample. The screening video supports MO3 most directly: participants who do not meet your criteria, or who were primed by a leading screener, are a source of confounded observations, and recognizing that at recruitment time is easier than diagnosing it in your results.
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.
A usability test is only as good as the tasks you ask people to do. A task scenario is a short, realistic situation that gives the participant a reason to use the interface — for example, "You want to meet a friend downtown on Friday night; find a restaurant that takes reservations and book a table for two" — rather than a direct instruction like "click the reservations button." Good scenarios supply just enough context to make behavior natural, avoid giving away the interface vocabulary or the navigation path, and end in a state you can actually observe and score.
This topic covers how to write those scenarios and assemble them into a test script. You will look at what separates a strong scenario from a leading or vague one, how to phrase context and prompts, how to attach measurable success criteria so you can later report completion rates, error counts, and time-on-task, how to pilot a script and revise wording that confuses participants, and how to sequence tasks so that earlier tasks do not teach participants the answers to later ones. The script also includes the non-task parts of the session: the introduction, consent, think-aloud instructions, and transitions.
As you watch, pay attention to three things: the exact wording used in example tasks (what is included, what is deliberately left out), how each speaker defines "done" for a task, and how the script is used as a facilitation tool during the session rather than just a planning document. Notice also how much preparation happens before a participant ever arrives.
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.
The think-aloud protocol asks participants to verbalize their thoughts while they work through tasks with an interface. Instead of guessing why a user hesitated, clicked the wrong button, or abandoned a flow, you hear their reasoning in the moment: what they expected, what label confused them, what they thought would happen next. The method rests on the idea that people can report the contents of their working memory as they perform a task, which makes it one of the richest sources of qualitative usability data available in a controlled test.
In this module you are learning to run a controlled session and capture clean data, so think-aloud is both a skill and a risk. Done well, it surfaces the reasoning behind errors and slowdowns. Done poorly, it biases behavior: leading prompts put words in the participant's mouth, over-talking slows the user and distorts time-on-task, and some tasks (highly practiced expert work, for example) simply break down when narrated. That is why the distinction between concurrent think-aloud (speaking while doing) and retrospective think-aloud (reviewing afterward, often with a screen recording) matters so much.
As you watch, pay attention to three things: the exact wording facilitators use to instruct and re-prompt participants, the moments where the facilitator deliberately stays quiet, and the signals that tell you concurrent think-aloud is not working and a different approach is needed. Also notice how session logistics -- consent, recording setup, note-taking, timing -- are built into the routine rather than improvised.
This short video from Nielsen Norman Group focuses on getting participants to actually think aloud: explaining the technique and its purpose at the start of a session, reinforcing the behavior when the participant does it well, and using gentle prompts to restart narration when they fall silent. Expect concrete examples of neutral prompt wording a facilitator can reuse. It covers the practical gap between telling someone to "think out loud" and getting usable verbal data.
It maps directly onto the "training participants" and "facilitator techniques" subtopics, and NN/g is a long-standing authority on usability testing practice, so the prompt wording it models is safe to adopt in your own sessions.
This video addresses the limits of the concurrent think-aloud method, particularly with work-domain experts whose tasks are fast, automatic, or cognitively demanding enough that narrating interferes with performance. It points to alternatives such as retrospective testing, expert walkthroughs, and interviews. The framing is about choosing the right method rather than forcing think-aloud into every study.
It is the clearest fit for the concurrent versus retrospective subtopic and directly supports the idea that a method can confound the data it is meant to collect -- an important judgment call for any test facilitator.
A checklist-style walkthrough of roughly ten things a moderator should do when running a usability study, covering the sequence of a session from setup through task facilitation. It situates think-aloud within the larger routine of moderating, including preparation, consent and recording, and neutral behavior during tasks. The checklist format makes it easy to turn into a session script of your own.
It provides the procedural wrapper around think-aloud -- standardized protocol, recording and capture, moderator neutrality -- which connects this topic to the rest of the controlled user testing module.
Together these videos build the facilitation skill set MO1 describes: the checklist video supplies the standardized session routine, and the "Help Users Think Aloud" video supplies the specific moderator moves for instructing, reinforcing, and re-prompting participants mid-task. For MO2, think-aloud is the qualitative stream that sits alongside completion rates, errors, and time-on-task, and these videos show how to elicit and capture it rather than hope it happens. For MO3, "When Thinking Aloud Fails" and the emphasis on neutral, non-leading prompts teach you to recognize when the method itself is contaminating the observation -- leading questions, expert tasks disrupted by narration, or talking that inflates time measures -- and to switch to retrospective or interview-based techniques to keep the data trustworthy.
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.
Quantitative data collection is the part of usability testing where you turn what happens in a session into numbers you can compare, report, and defend. The core metrics are familiar ones: whether a participant completed the task, how long it took, how many errors they made, and how difficult they said it felt. On top of these behavioral measures sit standardized attitudinal instruments such as the System Usability Scale (SUS) and the Single Ease Question (SEQ), which have been used widely enough that your scores can be compared against established benchmarks.
What makes these numbers trustworthy is not the arithmetic but the discipline behind it. You need a data collection instrument prepared in advance (a scoring sheet or form with explicit definitions of success, error, and start/stop points for timing), consistent administration across every participant, and a clear plan for how individual scores will be aggregated into summary values. Without that consistency, two observers watching the same session can record different results, and the resulting averages are meaningless.
The three videos below come from Nielsen Norman Group and cover the standardized questionnaires most often used in practice, how to choose between them, and the important caution about collecting metrics in small qualitative studies. While watching, pay attention to exactly when each instrument is administered, how scores are calculated and interpreted, and what sample size a metric realistically requires before you should treat it as a number rather than as a story about one user.
An introduction to the System Usability Scale, a ten-item survey given to participants at the end of a test session to capture perceived usability. The video is likely to explain the question format, how responses are converted into a single score, and how that score is interpreted against known benchmarks.
SUS is the single most widely used standardized usability questionnaire, so this directly supports the Standardized Usability Questionnaires subtopic, and NN/g is a recognized authority whose guidance on scoring and interpretation is reliable.
A short comparison of two standardized instruments: the System Usability Scale, administered once at the end of a session for overall benchmarking, and the Single Ease Question, asked immediately after each individual task. It discusses how each fits alongside qualitative methods and what kind of question each is suited to answer.
Choosing the right instrument and administering it at the right moment is central to designing data collection instruments and keeping measurement consistent across participants, which this video addresses directly.
This video addresses the common situation of wanting numbers from a small qualitative study. It explains that metrics from individual users can help illustrate how each person performed, while cautioning against treating averages from a handful of participants as statistically meaningful findings.
It gives students a realistic view of aggregating quantitative data and the limits of small-sample metrics, which is essential for distinguishing defensible numbers from misleading ones in the kinds of studies run in this course.
Together these videos give you the measurement side of a controlled test session. They supply concrete, standardized instruments (SUS and SEQ) and the timing rules for administering them, which supports facilitating sessions with consistent protocols (MO1) and collecting quantitative usability data alongside observational and think-aloud notes (MO2). The discussion of metrics in small qualitative studies also builds the judgment needed to recognize when numbers are valid versus when sample size or inconsistent administration has confounded them (MO3). Use them as a basis for the scoring sheet and post-task or post-test questionnaire you will prepare before running your own sessions.
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.
Qualitative data is everything you capture during a usability test that is not a number: what participants say as they think aloud, where they hesitate, the workarounds they invent, the confused facial expression before a misclick, and the explanations they give in a post-test interview. Where quantitative measures tell you that a task took 94 seconds or failed 4 times out of 10, qualitative data tells you why it happened and what the user believed was going on. Both are needed; neither is enough alone.
In this topic we look at how to capture that non-numerical evidence in a disciplined way. Structured observation and note-taking keep your records consistent across participants instead of dependent on memory. Post-test interviews and debriefs let you probe moments you noticed without leading the participant. Verbatim quotes and critical incidents (the specific breakdowns, errors, and moments of delight) become the evidence you cite in a findings report. Affinity diagramming is then the synthesis step: clustering dozens of raw observations into themes so that patterns, not anecdotes, drive your recommendations.
The three videos below come from Nielsen Norman Group, a long-standing UX research practice. They do not walk through a test session start to finish; instead they address the synthesis and interpretation side of qualitative work — how to organize what users say, think, feel, and do into a shared artifact, and how to classify the problems you observe. While watching, pay attention to the vocabulary used for categorizing raw observations, and think about how each technique would change the notes you take during a session. Ask yourself: what would I have to write down in the moment for this analysis method to work afterward?
A short explainer on the empathy-mapping technique, which organizes what you know about a user into quadrants covering what they say, think, do, and feel. The video describes how the mapping process distills scattered research knowledge into one place and how the resulting artifact serves as a quick reference for a team. Expect guidance on how the map is built and what each section is meant to hold.
The says/thinks/does/feels structure is a practical taxonomy for the types of qualitative data you collect in a usability session, and the clustering process it describes is closely related to affinity diagramming as a synthesis method.
This video breaks user pain points into three levels: interaction level, journey level, and relationship or organizational level. It explains how problems a user encounters can range from a small friction on a single screen to a larger breakdown across an entire experience. The framing helps you label the severity and scope of the problems you observe.
Documenting critical incidents requires a vocabulary for describing what kind of problem you just witnessed, and this gives you a clear, widely used classification to apply to your observation notes.
A companion piece focused on timing rather than technique: when in a project an empathy map is worth building. It covers using maps to plan an upcoming research study, to capture insights while research is underway, and to communicate findings to a wider team afterward.
It connects a synthesis artifact to the research workflow, which is exactly the decision you face when planning how to record and later report qualitative data from a controlled test.
These videos mainly support MO2 by sharpening how you treat the qualitative half of your data set — think-aloud utterances, observed behaviors, and inferred feelings — and by offering structures (empathy map quadrants, pain-point levels) for organizing raw notes into reportable findings. They indirectly support MO1, since knowing what you intend to capture shapes how you observe and what you probe during a debrief, and MO3, because classifying an observed problem by level forces you to ask whether it reflects a real interface issue or an artifact of the session setup. Pair them with the module readings on note-taking protocols and post-test interviewing, which cover the in-session mechanics the videos do not.
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.
Running a usability test is part research method and part live event management. Once participants are scheduled and tasks are written, your team still has to decide who facilitates, who takes notes, who handles recording and timing, how the room (or video call) is arranged, what you say in the first two minutes, and what you do when something goes wrong mid-session. This topic covers those practical logistics and the interpersonal dynamics that surround them.
These skills matter in this course because the quality of your data depends heavily on how the session is run. A facilitator who nudges a participant toward the right button, a noisy observer who reacts to a failure, or a missing consent step can all cost you an entire session's worth of usable results. Clear team roles, a stable environment, a consistent opening script, and a disciplined debrief are what make results from different participants comparable.
As you watch, pay attention to sequence and wording: what gets done before the participant arrives, the exact phrasing used to set expectations, how facilitators stay neutral when a participant struggles or asks for help, and what happens at the close of a session. Note where each video gives you something you could literally copy into your team's checklist or facilitator script for your own project sessions.
The companion video to the planning checklist, this one lists ten things to do while you are actually moderating a usability study. Expect coverage of facilitator behavior during the session, keeping the study on track, and the habits that lead to trustworthy research insights rather than contaminated observations.
This is the core video for team roles, in-session facilitation, and managing challenges as they arise, and its checklist format makes it easy to turn into a shared protocol your whole team follows.
The first of a two-part Nielsen Norman Group series, this video walks through ten things to do before you actually run a usability study. Based on the title and description, it covers the planning and preparation work that makes a session go smoothly, such as getting your study materials, tasks, equipment, and logistics in order ahead of time.
It maps directly onto the session environment setup subtopic and gives your team a concrete pre-session checklist; NN/g is a long-established usability research firm, so the guidance reflects standard professional practice.
A short demonstration in which facilitation experts show how to prepare a participant at the start of a test session, including the use of a facilitator's script. Rather than only describing the practice, it models the actual introduction so you can hear the tone and phrasing used.
It targets the opening the session subtopic directly, and seeing a scripted introduction performed is far more useful than reading about it when you have to deliver your own opening consistently across participants.
Together these three videos follow the arc of a real session: prepare (planning checklist), open the session with a consistent script (the introduction demonstration), and moderate without biasing the participant (moderating checklist). That sequence supports MO1 by giving you repeatable protocols and language for guiding participants through task scenarios. The emphasis on preparation and facilitator neutrality supports MO2, since reliable think-aloud commentary, timing, and error counts depend on a stable, well-equipped setup and a facilitator who does not interrupt or coach. Finally, the warnings implicit in both checklists about leading participants, technical problems, and inconsistent setups support MO3, helping you recognize when an observation has been confounded by the session itself rather than caused by the interface.
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.
Once a usability test session ends, you are left with a messy pile of evidence: session notes, observer tallies, recordings, think-aloud quotes, task timings, and error counts. Compiling structured results is the work of turning that raw material into something a design team can act on. It involves organizing data by participant and by task, grouping individual observations into recurring usability problems, rating those problems by severity, and then assembling a report that pairs numbers with illustrative evidence and concrete recommendations.
This matters in CEN3722 because a usability test only has value if its findings reach the people who build the interface in a form they can use. A report that lists forty unsorted observations with no prioritization gives a team no idea where to start. A report that states results more confidently than the data warrants can push a team toward the wrong redesign. Your job is to be both useful and honest: clear about what you found, clear about how strong the evidence is, and clear about what should change.
The three videos below come from Nielsen Norman Group, a long-established usability consultancy. As you watch, focus on three things: how severity criteria help you decide what to report first, how to describe findings truthfully when sample sizes are small, and how framing and context affect whether your audience actually engages with your recommendations. Take notes you can apply directly to your team's results document.
This short video explains how to assign severity ratings to usability problems found during usability studies or heuristic evaluation, using a small set of criteria rather than gut feeling. Expect discussion of factors such as how often a problem occurs, how badly it blocks users, and how persistent it is across a task. The result is a prioritized list rather than an undifferentiated set of observations.
Severity rating is the bridge between raw observations and an actionable report, which makes this directly relevant to identifying usability problems and patterns and to structuring the results document around priority.
This video addresses how to present research results to stakeholders truthfully and responsibly, including how to avoid overstating what a small study can support. It is likely to touch on careful use of numbers and percentages, appropriate hedging, and being transparent about method and sample. The emphasis is on communicating findings without distorting them.
It speaks directly to presenting quantitative findings honestly, a common failure point when student teams report percentages from five or six participants.
This video covers how to set the stage with stakeholders before presenting UX design or research work so that the feedback you receive is useful. It discusses providing context, framing what kind of input you are seeking, and structuring the conversation around the goals of the work. The focus is on the presentation setup rather than the findings themselves.
Presenting qualitative findings and recommendations is a conversation, not just a document, and this video shows how framing and context shape whether your recommendations get a serious hearing.
These videos extend the module's data collection work into the reporting stage. Having facilitated sessions (MO1) and gathered both quantitative measures such as task completion, errors, and time-on-task alongside qualitative think-aloud observations (MO2), students need a disciplined way to compile both kinds of evidence into one structured document. The severity rating video supplies criteria for turning scattered observations into prioritized problems; the responsible presentation video reinforces the MO3 concern for data integrity by showing how to report findings without overstating what the data supports; and the feedback video helps students deliver recommendations in a way that stakeholders can engage with productively.
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.