Iterative redesign is the engine of user-centered design. Rather than treating a design as something you get right once, iterative practice treats every version as a hypothesis: you build it, put it in front of users, learn where it fails, change it, and test again. Each pass through this cycle should be smaller, more focused, and better informed than the one before it.
In this module you are working with real testing results, so the key question becomes what to do with them. Some findings call for targeted refinement — a label, a control, a step in a flow — while others reveal that the underlying concept or structure is wrong and a wholesale rethink is cheaper than patching. Deciding which situation you are in, recording why you made the change (your design rationale), and defining in advance what "better" would look like in the next round are the skills this topic develops.
As you watch, look for three things: how each speaker describes the loop itself (what happens at each stage and what triggers another pass), how they distinguish refining an existing idea from exploring alternative ideas, and how testing is positioned as a source of evidence rather than opinion. Note also how different process models — design thinking, agile — frame iteration, since the vocabulary differs even when the underlying cycle is similar.
A short Nielsen Norman Group talk arguing that generating more design options leads to better outcomes, and comparing three strategies for doing so: iterative design (improving one concept across rounds), parallel design (developing several concepts side by side), and competitive testing (learning from existing products). Based on the title and description, it addresses how teams combine these approaches to move quickly rather than treating them as mutually exclusive.
NN/g is a leading authority in usability research, and this video directly frames the choice between refining one design and exploring alternatives — the core of the targeted versus wholesale redesign distinction.
This video places usability testing within the design thinking process, picking up after prototyping to explain how testing validates the assumptions made in earlier stages. It is likely to cover what happens when testing reveals problems and how findings send the team back into earlier phases of the process.
It supplies the cyclical framing the topic depends on: testing is not an endpoint but the step that feeds the next iteration, which is exactly how the design cycle should be understood.
An Interaction Design Foundation video featuring Laura Klein that contrasts agile and waterfall approaches to software development and explains what an agile model means for UX work. Expect discussion of why working in short, repeated cycles with feedback differs from planning everything up front in a single linear pass.
It gives the process-level case for iteration over one-shot design and connects incremental cycles to the idea of setting goals for each round of work.
Together these videos build the conceptual frame students need before acting on their own test data. The design thinking video reinforces that testing findings loop back into design rather than closing it out, supporting the analysis work in MO1. The NN/g video on iterative, parallel, and competitive design gives students a basis for judging whether a finding warrants a focused fix or a fresh alternative, which underpins the prioritization decisions in MO2. The agile versus waterfall discussion models working in short, goal-bounded cycles, reinforcing MO3's expectation that revisions are made deliberately, one iteration at a time, with reasons that can be stated and defended.
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.