Iterative design
Iterative design is a process of creating a design, testing it with users, and revising it through repeated cycles. Each cycle uses evidence from the previous version to improve how well the design solves the user's problem.
How it works
Start with a specific task, such as finding a product or opening an account. Build something people can try, observe where they struggle, and change the design before testing again.
The first version can be a paper sketch or clickable prototype, not finished software. For a startup, this means testing a risky assumption before paying to build it.
ISO 9241-210, the human-centred design standard, treats iteration as a core part of the design process.
Testing a shorter sign-up form
In a hypothetical test, 10 target users try to create an account. Four abandon the form after mistaking optional fields for required ones. The team removes those fields and tests the revision with 10 different target users doing the same task.
| Version | Users who finish | Completion rate |
|---|---|---|
| Original form | 6 of 10 | 60% |
| Shorter form | 9 of 10 | 90% |
The observed increase is 90% − 60% = 30 percentage points. These small tests help identify usability problems; they do not establish the improvement across the whole customer base.
The useful output is a design decision backed by observed behavior, not simply another version.
Questions people ask
What are the benefits of iterative design?
It exposes confusing steps before they become expensive to change. Teams can test alternatives instead of settling disagreements by opinion. The limit is what you test: making sign-up easier does not prove people want the product.
What are the five steps of the iterative process?
There is no universal five-step formula. A common design loop is: understand the problem, create a design, build a prototype, test it, and refine it. Teams repeat or revisit steps as they learn, rather than treating them as a fixed checklist.
