What is Iteration?

TL;DR

• Iteration means improving a product through repeated cycles.
• Each cycle should incorporate new evidence or a clearer hypothesis.
• Iteration is not random polishing or changing things for taste.
• Fast iteration lowers the cost of being wrong.
• Good teams know what they are trying to learn from each version.

What does iteration look like?

A team prototypes an onboarding flow, observes users missing the team-invite step, changes the hierarchy, tests again, then ships the improved version and watches activation data.

Each version responds to evidence from the previous one.

Iteration vs. rework

Iteration is intentional learning. Rework often happens because requirements, context, or implementation were unclear.

Both involve change, but iteration should increase understanding rather than simply repeat effort.

What can trigger an iteration?

• user research
• usability findings
• product analytics
• technical constraints
• new edge cases
• market changes
• stakeholder feedback grounded in evidence

How do teams iterate well?

1. State the problem or hypothesis.
2. Create the smallest meaningful change.
3. Define what evidence would indicate improvement.
4. Test or ship it.
5. Measure what changed.
6. Decide whether to continue, revert, or try another direction.

Common mistakes

Changing several variables at once

Then the team cannot tell what caused the result.

Iterating forever without a decision

Teams still need thresholds for moving forward.

Only polishing visual details

Iteration can target problem framing, flow, content, state coverage, or interaction logic.

The bottom line

Iteration asks: what did we learn from this version, and what should change in the next one because of that evidence?

Related terms

Prototyping · Prototype · A/B testing · Product discovery

Relevant Figr resource

Read UX Design Process Steps for iteration across discovery, design, and delivery.