Up to this point in the module you have been building a functional prototype and drafting a user testing plan as if they were two separate deliverables. In practice they are one system: every task you ask a participant to perform must be supported by something that actually works in the prototype, with realistic data already loaded and the interface in a known starting state. Integrating prototype and testing preparation means walking through your protocol task by task and confirming that the build can carry it, trimming scope where it cannot, and deciding in advance what the prototype should look like the moment a participant sits down.
This topic covers three practical concerns. Aligning prototype scope with test tasks is about mapping each task script step to a screen, control, or flow that exists; anything unsupported either gets built, faked deliberately, or cut from the protocol. Preparing test data and prototype state covers seeding accounts, sample content, and default settings so sessions are comparable, plus the reset procedure between participants. Coordinating team roles across development and testing means naming who finishes the build, who facilitates, who takes notes, and who owns the pilot run that catches problems before real participants arrive.
The three videos below approach preparation from complementary angles: a research-practice checklist of pre-session work, a designer's end-to-end walkthrough of one usability study, and a set of best practices for running sessions well. While watching, keep your own project in mind and note anything that implies a prototype requirement — a piece of test data, a reset step, a role to assign, or a task you may need to narrow.
A short checklist-style video from Nielsen Norman Group covering ten things to do before you actually run a usability study. Based on its title and description, it should walk through planning steps such as clarifying research goals, writing and reviewing tasks, recruiting the right participants, and preparing materials and logistics in advance. It is presented as the first of a two-part set, with this half focused entirely on preparation rather than execution.
NNgroup is a long-established usability research organization, and a checklist framing maps directly onto the preparation work this topic requires. It is the most direct fit for aligning prototype scope with test tasks, since the checklist items tell you what must exist and be verified before testing day.
A practitioner walkthrough in which the creator explains her own process for planning, conducting, and synthesizing a usability testing session. Expect to see how a study is set up end to end, likely including preparing the test material and tasks, running the session, and turning observations into findings. Because it follows one project, you can see how the planning decisions connect to what actually happens in the session.
Seeing a complete start-to-finish example helps you understand why preparation choices matter downstream, which reinforces the idea that the prototype and protocol are built together. It is a useful model as you assemble your own task script and data collection instruments.
Maze presents five best practices intended to help teams gather accurate, ethical, and actionable usability insights. The description suggests coverage of things like framing tasks and questions neutrally, treating participants ethically, and avoiding common mistakes that distort results. Practices of this kind usually depend on groundwork done before the session begins.
Best-practice guidance highlights the conditions a session needs in order to produce trustworthy data, which in turn drives how you seed test data and set the prototype's starting state. It also helps clarify facilitation expectations, useful when dividing roles across your team.
Together these videos bridge MO1, MO2, and MO3. The NNgroup checklist and the Maze best practices give you concrete criteria for a defensible testing plan with task scripts, participant criteria, and data collection instruments (MO2), while also surfacing the pre-session verification work that confirms your prototype can support every planned task (MO3). The practitioner walkthrough shows the whole cycle in context, helping you judge which core features your build must genuinely implement versus simulate (MO1), and reinforcing that prototype readiness, test data, prototype state, and team role assignments should all be settled before the first participant 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.