Iteration
Iteration is a repeating cycle of designing, testing, and improving a product. Each cycle delivers concrete insights from users, which are used to refine the product step by step. It is a core principle of agile development and UX design, replacing the attempt to get a perfect result on the first try.
An iterative approach isn’t just a buzzword. It is a proven, more effective way to build digital products:
- Each iteration improves usability by tens of percent. Across 4 case studies, Nielsen Norman Group found a median overall usability improvement of 165%. The median improvement per iteration was 38%, with the biggest jump between the first and second version (45%) (NNGroup – Iterative Design)
- Iterative (agile) projects succeed 3× more often. In its CHAOS 2020 report, the Standish Group analyzed more than 50,000 technology projects and found a success rate of 42% for agile projects versus only 13% for waterfall projects (Standish Group – CHAOS Report 2020)
- Iteration has a measurable business impact. McKinsey tracked 300 companies over 5 years. Companies that iterated systematically achieved 32 percentage points higher revenue growth (McKinsey – The Business Value of Design, 2018)
- Faster time to market. In a study for IBM, Forrester found that teams using iterative design thinking got to market 2× faster and cut design and development time by up to 75%. ROI reached 301% over three years (Forrester – TEI of IBM Design Thinking, 2018)
FAQ
How many iterations does it take to get a good result?
Nielsen Norman Group recommends at least 3 iterations. The data shows that the first iteration brings the biggest improvement (a median of 45%), but later cycles still uncover problems the previous version didn’t solve.
What is the difference between iteration and agile development?
Iteration is the underlying principle: a repeated “design, test, improve” cycle. Agile development is a specific project management methodology that uses iteration as its building block (typically in sprints of 1–4 weeks). You can iterate without a formal agile framework, too.
Isn’t iterating more expensive than getting everything right the first time?
Quite the opposite. Forrester’s study for IBM showed a 301% return over 3 years and up to 75% shorter development time. Fixing errors after launch is orders of magnitude more expensive than catching them during iterations. The Standish Group also shows that non-iterative (waterfall) projects fail 59% of the time.
Sources:
- NNGroup – Iterative Design of User Interfaces – 4 case studies, median improvement of 165%
- Standish Group – CHAOS Report 2020 – analysis of 50,000+ projects
- McKinsey – The Business Value of Design (2018) – 5-year study of 300 companies
- Forrester – TEI of IBM Design Thinking (2018) – 301% ROI
%201.webp)