What are the 5 stages of product design?
Written by
Passionate Designer & Founder
The 5 stages of the product design process are: discover, define, ideate, prototype, and test. Most descriptions stop there. What they skip is how each stage maps to a specific business risk, and ignoring that sequencing is why most scale-ups ship features users don't want and decks that don't convert.
Stage 1 is discovery. You're not designing anything yet. You're mapping the problem space: customer interviews, usage data, competitor positioning, support tickets. For a Series-B SaaS we worked with last year, discovery revealed that 60% of churn was happening at onboarding, not at the feature layer. The fix wasn't a UI redesign. It was a restructured activation flow. You can't see that without a real discovery phase.
Stage 2 is definition. You're narrowing from everything you learned to a specific problem worth solving. This is where positioning enters the product design process. If your product competes in a crowded category, the problem you choose to solve is a positioning decision. Most design processes treat this as a UX exercise. It isn't. It's strategy.
Stage 3 is ideation. This is where most teams rush. They generate 3 concepts, pick the one the founder likes, and call it done. Proper ideation runs at least 8 to 12 distinct directions before any filtering. We use structured How Might We exercises paired with constraint mapping: what are we not allowed to change, and what's genuinely open.
Stage 4 is prototyping. The mistake I see most often here is building a prototype that's too high-fidelity too fast. A Figma prototype at 80% polish costs 3x as long to revise as a low-fidelity flow. Start rough. Test the logic, not the aesthetics.
Stage 5 is testing. Not with your team. Not with your investors. With the people who will actually pay for the product. Five unmoderated user tests will surface 80% of critical usability failures, based on Nielsen Norman research across hundreds of studies.
What the standard framework misses
The stages are not linear for growth-stage companies. A company at €5M ARR is running stages 1 and 5 simultaneously on different parts of the product. Discovery never fully stops. Testing never waits for a clean handoff.
The deeper gap is that most frameworks treat the product design process as isolated from everything around it: the sales deck, the website, the demo. If your product UI tells a different story than your positioning, buyers see four different companies instead of one. That's a fragmentation problem, not a design problem. No amount of good execution fixes a strategy that was never there to begin with. For UX design work that connects to commercial outcomes, that upstream lever is what actually moves the number. When you're ready to map this out for your product, book a 20-min intro. For the full guide, read our product design process overview.
