Theory
Nobody gets it right the first time
Your FestConnect testing produced a ranked list of problems. Here is the humbling truth behind the whole subject: those problems are NORMAL. No designer, however good, gets it right on attempt one. The first design is always a hypothesis, and testing proves it partly wrong.
So the professional does not despair or defend: they ITERATE. Fix the date field, test again, find the design is better but a label now confuses people, fix that, test again. Iterative design is this loop, and it is how every good product is actually made: not by genius, but by cycles.
Theory
Sculpting, not printing
A printer produces the finished thing in one pass: if the file was wrong, so is the print. That is linear design: design once, ship, hope.
A sculptor works in PASSES: rough shape, step back, refine, step back, refine: the statue emerges through repeated cycles of doing and evaluating. That is iterative design. You do not carve a masterpiece in one stroke; you converge on it, cycle by cycle, each pass guided by looking at what you have.
Theory
Iterative design, formally
Iterative design is a cyclical, repeating process: design → prototype → test with users → gather feedback → refine → and repeat. Each pass through the loop is an iteration, and each one improves the design based on EVIDENCE.
It is the opposite of a linear (one-shot) approach where you design once and ship, hoping it works. Iteration accepts that first attempts are flawed and uses user feedback as the engine to progressively close the gap between the design and users' real needs.
This loop is the UCD cycle from Unit 1 in action (understand, design, evaluate, repeat): iteration is where user-centered design actually happens.
Theory
Feedback is the fuel; fail small and early
An iteration needs INPUT to improve, and that input is user feedback from many sources: usability tests, interviews, analytics, reviews, support tickets, A/B tests.
The deep payoff connects to the cost-of-change curve: iteration lets you fail small and early rather than big and late. A flaw found in iteration 2 of a prototype costs a tweak; the same flaw discovered after a full public launch costs lost users and a scramble. Cheap, frequent cycles catch problems while they are still cheap.
And iteration does not stop at launch: real products keep iterating forever, continuously improving as they learn more about users.
Quiz
What best describes iterative design?
- Design the product perfectly once, then ship it unchanged
- A repeating cycle of design, test, gather feedback and refine, improving the product each round
- Letting users write the code themselves
- Adding features until the deadline, without testing
- Designing only the visual layer and ignoring function
Show the answer
A repeating cycle of design, test, gather feedback and refine, improving the product each round
Iterative design is the LOOP: design, prototype, test with users, gather feedback, refine, and repeat, with each cycle improving the product based on evidence: the sculptor's passes, not the printer's single shot. Option A is the linear/waterfall opposite that iteration exists to replace (first designs are never perfect). Option C confuses user FEEDBACK (input) with users doing the design (they do not). Option D describes deadline-driven feature-cramming without the test-and-refine core. Option E ignores that iteration improves the whole experience, not just visuals. The essence: improve in evidence-driven cycles, because you never get it right the first time.
Think first
Why iteration beats one perfect plan
A manager says 'let us just design FestConnect perfectly up front so we never need to change it, saving all this testing time.' Why is this tempting plan actually riskier and more expensive? Then tap.
Show the answer
Because 'perfect up front' is impossible: you CANNOT know how real users will behave until they use it, so a big one-shot design bakes in assumptions that only reveal themselves as flaws AFTER launch, when fixing is most expensive and users have already walked away. Iteration is not wasted time; it is RISK MANAGEMENT: many small, cheap corrections instead of one huge, late, costly one (the cost-of-change curve). Paradoxically, trying to skip iteration to save time usually costs far MORE time and users. The mature stance: you will be wrong; the only choice is whether you find out cheaply and early, or expensively and late.
Watch out
Iteration slips
One-and-done design: shipping the first version untested assumes you got it right (you did not).
Iterating without feedback: changing things by opinion, not evidence, is not iteration: it is guessing in circles.
Unfocused iterations: each cycle should target the PRIORITISED issues from testing, then retest, not randomly tweak.
Stopping at launch: good products iterate continuously, even after release.
Defending the design: treat critique as fuel, not attack; the goal is a better product, not a right designer.
Theory
Better for most is not enough
Iteration converges FestConnect toward working smoothly for the users you tested. But 'works for most users' can still lock OUT people with disabilities: those who cannot see the colour, hear the sound, or use a mouse. Making a product work for EVERYONE is the next, essential lesson: designing for ACCESSIBILITY: not an add-on, but part of getting it right. Then the subject closes with a full case study.
Summary
Key takeaways
- Iterative design is a repeating cycle: design, prototype, test, gather feedback, refine, repeat.
- Each iteration improves the design based on evidence; it is the opposite of a linear one-shot approach.
- First designs are always flawed; user feedback progressively closes the gap to real needs.
- Feedback comes from usability tests, interviews, analytics, reviews, support, A/B tests.
- Iteration lets you fail small and early (cost-of-change), not big and late, and continues after launch.
- Each cycle should focus on the prioritised issues from testing, then retest.
- Memory hook: sculpt in passes, do not print in one shot.