What is Iteration?
Iteration is the practice of building something small, shipping it to real users, measuring the result, and using that learning to inform the next version. Each cycle produces a better version of the product. Over time, iteration converges on something that works.
The alternative to iteration is big-batch development: spend six months building, launch everything at once, and hope users like it. Iteration reduces the blast radius of wrong decisions by catching them early.
Why Iteration Matters
No PM gets the product right on the first try. User behavior is unpredictable, requirements are ambiguous, and market conditions shift. Iteration accepts this reality and builds a process around it.
The lean startup movement formalized iteration as the build-measure-learn loop. Ship an MVP, measure how users respond, learn what to change, and build the next version. Each cycle takes days or weeks, not months.
How to Iterate Effectively
Start with a clear hypothesis for each iteration. "This change will increase onboarding completion by 10%." Without a target, you are tweaking randomly.
Ship the smallest useful change. The goal of an iteration is to learn, not to ship a polished feature. Get something in front of users quickly, even if it is rough.
Measure immediately. Use product analytics to track whether the change moved your target metric. Do not wait weeks to look at results.
Decide: double down, pivot, or kill. If the iteration moved the metric in the right direction, keep going. If it did not, change your approach or move on to a higher-impact problem.
Iteration in Practice
Instagram started as Burbn, a location-based check-in app. Through rapid iteration and user observation, the team noticed that photo sharing was the most-used feature. They iterated away from everything else and launched Instagram.
Spotify's squad model is designed for fast iteration. Each squad owns a feature area and ships weekly. They use feature flags to release changes to small user groups, learn from the data, and iterate before rolling out broadly.
Common Pitfalls
- Iterating without measuring. Shipping new versions without checking whether they improved anything is just shipping, not iterating.
- Too many changes per iteration. Change one thing at a time. Otherwise, you cannot attribute the result to a specific change.
- No stopping condition. Define when you are done iterating. Perfection is not a shipping milestone.
- Confusing activity with progress. Five iterations that each improve the metric by 0.1% might not be worth it. Focus iteration on high-impact areas.
Related Concepts
Iteration is the core mechanism of agile development and lean startup methodology. It is executed through sprints in Scrum. Continuous discovery extends iteration beyond engineering into research and design. Feature flags enable safe iteration by controlling rollout.