The Product Design Process: 7 Stages From Discovery To Design System
Lily Roberts
Senior Marketing Strategist
10.10.2026
Short answer: The product design process is the sequence a team follows to turn a user problem into a shipped digital product: discovery and research, define, ideate, prototype, test, build and handoff, then iterate and maintain a design system. Each stage has its own deliverables, from research reports and problem statements to tested prototypes and developer-ready specs. Most teams loop through the middle stages several times rather than running them once in a straight line.
A clear product design process is what separates teams that ship features users adopt from teams that ship features users ignore. It gives designers, product managers and engineers a shared vocabulary for where a piece of work sits, what “done” looks like at each step, and when it is safe to commit engineering time.
This guide breaks the process into seven practical stages, with the activities, deliverables and typical duration of each. It also covers the frameworks most teams borrow from (the Double Diamond and design thinking), how product design differs from UX and UI design, who sits on a product design team, which tools show up at each stage, and how the process changes for startups versus enterprises.
Product design, in the software sense, is the work of deciding what a digital product should do, how it should behave and how it should look, so that it solves a real user problem and supports a business goal. A product designer is accountable for the whole experience of a feature or product: the research behind it, the flows and interactions, the interface, and how it performs after launch.
Digital product design sits between three concerns: what users need, what the business can sell or sustain, and what engineering can build in a reasonable time. Good product designers spend as much time on problem framing, trade-offs and measurement as they do in Figma.
One clarification: industrial product design (designing physical objects such as furniture, appliances or devices for manufacture) is a different discipline with its own process, tools and training. This guide covers software and digital products only.
The 7 Stages Of The Product Design Process
The stages below describe a typical project for a new product or a significant feature. Durations assume a small dedicated team and will stretch or compress with scope. In practice, stages overlap and teams loop back when testing reveals a wrong assumption.
1. Discovery And Research
Discovery establishes what problem is worth solving, for whom, and why now. The goal is evidence, not opinion: who the users are, what they are trying to get done, what they use today, and where they struggle.
Activities: stakeholder interviews, user interviews, contextual inquiry, analytics and support ticket review, competitor analysis, a heuristic review of the current product if one exists.
Deliverables: a research plan, interview notes and synthesis, personas or jobs-to-be-done statements, a current-state journey map, a competitive landscape.
Typical duration: 1 to 4 weeks.
If you need help picking methods, our guide to UX research methods covers when to use interviews, surveys, diary studies, card sorting and more.
2. Define
Define turns research into a sharp problem statement and a set of constraints. This is where teams agree on scope, success metrics and what they are deliberately not doing.
Activities: affinity mapping, insight synthesis workshops, prioritization (for example impact vs effort), writing “how might we” questions, setting success metrics.
Deliverables: a problem statement, a product or design brief, prioritized requirements or user stories, success metrics and guardrails.
Typical duration: 3 days to 2 weeks.
3. Ideate
Ideation generates many possible solutions before narrowing to a few worth prototyping. The emphasis is on breadth first, then convergence based on the criteria set in the define stage.
Activities: sketching sessions, design studios, “crazy eights”, user flow mapping, information architecture work, early concept reviews with engineering to catch feasibility issues.
Deliverables: sketches, user flows, site maps or information architecture diagrams, low-fidelity wireframes, a short list of concepts.
Typical duration: 1 to 2 weeks.
4. Prototype
Prototyping makes the chosen concepts tangible enough to test. Fidelity should match the question you are asking: a clickable wireframe is enough to test navigation, while testing trust or visual comprehension needs something closer to the final interface.
Activities: wireframing, interaction design, visual design explorations, building clickable prototypes, writing realistic content rather than placeholder text.
Deliverables: mid- or high-fidelity mockups, an interactive prototype, a test script aligned with the prototype.
Typical duration: 1 to 3 weeks.
5. Test
Testing checks whether real users can complete the key tasks and whether the design moves the metrics you care about. Small rounds of moderated or unmoderated testing catch most serious issues before any code is written.
Activities: moderated and unmoderated usability testing, first-click and preference tests, accessibility checks, concept validation with target customers.
Deliverables: a findings report with severity ratings, video clips of key moments, a prioritized list of design changes.
Typical duration: 1 to 2 weeks per round, often repeated.
Our usability testing guide walks through planning, recruiting, running sessions and reporting.
6. Build And Handoff
Handoff is where most quality is won or lost. Modern teams treat it as collaboration rather than a single file transfer: designers stay involved through implementation, answer questions, and review builds against the design.
Activities: annotating specs, defining states (empty, loading, error, edge cases), responsive behavior, design QA of staging builds, pairing with engineers on tricky interactions.
Deliverables: developer-ready design files, redlines or inspect-ready specs, an interaction and motion spec, exported assets, acceptance criteria.
Typical duration: runs alongside development, usually 2 to 8 weeks for a feature.
If your team works in Figma, our guide to Figma Dev Mode explains how developers inspect designs and how it fits into a handoff workflow.
7. Iterate And Maintain A Design System
Launch is the start of a new learning loop, not the end of the process. Teams measure adoption and task success, gather feedback, and feed what they learn back into discovery. In parallel, the components and patterns that proved themselves get documented in a design system so the next feature is faster and more consistent.
Deliverables: a post-launch report, an updated roadmap, a design system (design tokens, a component library, usage guidelines, accessibility rules) kept in sync with the coded components.
Typical duration: ongoing; a first design system foundation often takes 1 to 3 months to establish.
Stages, Deliverables And Who Is Involved
Use this table as a quick reference when planning a project or reviewing a vendor proposal. If a proposal skips a row entirely, ask why.
Stage
Key Deliverables
Who Is Involved
Typical Duration
Discovery and research
Research synthesis, personas or JTBD, journey map, competitive review
Design system team, product designers, engineers, PM, analytics
Ongoing
Frameworks Behind The Process: Double Diamond And Design Thinking
Most product design processes, including the seven stages above, are adaptations of two well-known frameworks. Knowing where they come from helps when you need to explain your process to stakeholders or compare agency methodologies.
The Double Diamond
The Double Diamond was developed by the UK Design Council as a common way to describe the design process. It has four phases: Discover, Define, Develop and Deliver. The two diamonds represent two rounds of divergent and convergent thinking: first exploring the problem widely and narrowing to a clear definition, then exploring many solutions and narrowing to one that works.
The Design Council has since folded the Double Diamond into a broader Framework for Innovation, which acknowledges that teams often prototype during discovery, return to earlier phases when deeper problems appear, and that digital products are never really “finished.” That last point maps directly to stage 7 in this guide.
The Design Thinking Process
Design thinking is the human-centered problem-solving approach popularized by the design firm IDEO and by Stanford’s d.school (the Hasso Plattner Institute of Design, founded by IDEO co-founder David Kelley). The d.school’s Design Thinking Bootleg describes five modes: Empathize, Define, Ideate, Prototype and Test.
Nielsen Norman Group’s design thinking framework adds a sixth phase, Implement, which is closer to how product teams actually work. NN/g also credits David Kelley and Tim Brown of IDEO, with Roger Martin, for coining the term in the 1990s.
How They Map To The 7 Stages
Discovery and research lines up with Discover (Double Diamond) and Empathize (design thinking).
Define is Define in both frameworks.
Ideate and prototype sit inside Develop, and match Ideate and Prototype.
Test spans Develop and Deliver, and matches Test.
Build and handoff and iterate extend Deliver and NN/g’s Implement into the ongoing life of a software product, which neither original model spells out in detail.
Neither framework is a rulebook. Treat them as shared language, and adapt the steps to your product’s risk, timeline and maturity.
Product Design vs UX Design vs UI Design
The three titles overlap heavily and companies use them inconsistently. A useful way to separate them is by scope of accountability: UI design owns the interface, UX design owns the experience of using it, and product design owns the experience plus its business outcome.
Dimension
Product Design
UX Design
UI Design
Core question
Should we build this, and does it move the business?
Can people accomplish their goal easily?
Is the interface clear, consistent and attractive?
Scope
End-to-end product or feature, from problem to post-launch metrics
User flows, structure, interactions and usability
Visual layout, typography, color, components and states
Typical outputs
Problem framing, flows, prototypes, specs, success metrics
Research, journey maps, wireframes, prototypes, test findings
In smaller companies, one “product designer” usually covers all three. In larger organizations, the roles split, and product designers lean on specialists for research and visual design.
Roles On A Product Design Team
Not every team needs every role. A seed-stage startup may have one designer doing everything; a large enterprise may have dozens of specialists. These are the roles you will see most often:
Product designer: owns a feature or product area from problem framing through handoff and post-launch iteration.
UX researcher: plans and runs studies, synthesizes findings, and keeps the team honest about evidence.
UI or visual designer: focuses on interface craft, visual systems and polish.
Interaction or motion designer: defines how elements respond, transition and animate.
Content or UX writer: writes interface copy, error messages and onboarding, and shapes terminology.
Design system designer or engineer: builds and maintains the shared component library, tokens and documentation.
Design lead or head of design: sets quality standards, staffs projects, and represents design in roadmap decisions.
Product manager and engineering lead: not designers, but core partners at every stage, especially define and handoff.
Product Design Tools By Stage
Tooling matters less than process, but it shapes how fast a team can move between stages. The tools below are common examples, not recommendations. Features and plans change often, so check each vendor’s own site before committing.
Discovery and research: research repositories such as Dovetail for tagging and synthesizing interviews; video call tools for remote interviews; product analytics tools for behavioral data; survey tools for quantitative input.
Define and ideate: online whiteboards such as FigJam or Miro for affinity mapping, flows and workshops; shared docs for briefs and problem statements.
Prototype: interface design tools such as Figma for wireframes, mockups and clickable prototypes; code-based prototyping tools when interactions need to feel real.
Test: unmoderated testing platforms such as Maze or similar services for task-based tests, first-click tests and surveys on top of prototypes; screen recording for moderated sessions.
Build and handoff: developer inspection features such as Figma Dev Mode, plus issue trackers for acceptance criteria and design QA tickets.
Iterate and design system: shared component libraries in the design tool, a coded component library and a documentation site, plus analytics and experimentation tools to measure results.
How The Process Changes For Startups vs Enterprise
The seven stages apply at any size, but how much time each one gets, and who signs off, varies a lot.
Startups
Compressed stages: discovery may be a handful of customer calls; define may be a one-page brief. Whole cycles can run in 2 to 4 weeks.
Ship to learn: early-stage teams often test with real users in production, using feature flags and analytics, rather than polishing prototypes.
Lightweight design system: a small component library and a few rules beat a full system that nobody has time to maintain.
Main risk: skipping research entirely and building for the founder’s assumptions rather than the market’s needs.
Enterprise
More stakeholders: legal, security, compliance, brand and accessibility reviews add steps and calendar time.
Formal research operations: dedicated research teams, participant panels and consent processes.
Mature design systems: a dedicated team maintains tokens and components across many products, and new work is expected to use them.
Main risk: process overhead that slows learning, so teams spend months on a feature before any user sees it.
A practical middle ground for both: match the depth of each stage to the cost of being wrong. A pricing page redesign deserves more testing than a settings toggle.
How Long It Takes And What Outsourcing Costs
Adding up the stage durations above, a focused project for a new feature or a minimum viable product typically runs 6 to 16 weeks from discovery to handoff, with build and iteration continuing after that. A full product redesign, or a first design system for a multi-product company, can take several months.
Published price ranges for outsourced product design vary so widely between sources that a single figure would mislead more than it helps. Agencies price by team size, seniority, location and duration, so the useful thing is to understand what drives a quote:
Scope: a discovery sprint, a single feature, an MVP and an end-to-end redesign are very different engagements.
Research depth: recruiting niche participants (for example clinicians or enterprise IT buyers) costs far more than testing with general consumers.
Team composition: a single senior designer costs less per week than a pod with a researcher, product designer, UI designer and design lead.
Location and seniority: rates differ significantly between regions and between senior and mid-level staff.
Engagement model: fixed-scope projects carry a risk premium; monthly retainers or dedicated teams spread cost over time.
Design system work: building or extending a component library, especially with coded components, adds significant effort.
When comparing proposals, ask each vendor to price the same scope broken down by stage. It makes gaps (such as no testing budget) obvious.
When To Hire A Product Design Agency
An outside team makes sense when the cost of getting the product wrong is higher than the cost of the engagement, and when you cannot staff the work internally in time. Common triggers include:
You are building a new product or MVP and have no in-house designers yet.
Your team has engineers and PMs but no one experienced in research or usability testing.
A redesign or platform migration needs extra capacity for a defined period.
You need an independent view of why a product is underperforming before deciding what to fix.
Your interface has grown inconsistent and you need help establishing a design system.
For end-to-end work, start with our list of the top product design agencies. If the gap is evidence rather than design capacity, the top UX research and usability testing agencies can run discovery and testing rounds alongside your in-house team. And if you mainly need a diagnosis of an existing product, consider one of the top UX audit companies before committing to a full redesign.
Whichever route you take, ask candidates to walk through their process stage by stage, show real deliverables from past projects, and explain how they hand off to engineering and measure results after launch.
Frequently Asked Questions
What Are the Stages of Product Design?
The common product design stages are discovery and research, define, ideate, prototype, test, build and handoff, and iterate (including maintaining a design system). Some teams merge stages or use the four Double Diamond phases instead. The stages repeat, so a single feature may pass through ideate, prototype and test several times.
What Is Digital Product Design?
Digital product design is the design of software products such as web apps, mobile apps and SaaS platforms. It covers research, interaction design, interface design and measurement of outcomes. It differs from industrial design, which deals with physical products made for manufacture.
What Is the Difference Between Product Design vs UX Design?
UX design focuses on how easy and pleasant a product is to use. Product design includes that work but also owns business outcomes, such as adoption and retention, and is involved in deciding what gets built. In many companies the titles are used interchangeably.
Is the Design Thinking Process the Same As the Product Design Process?
They are closely related. The design thinking process (empathize, define, ideate, prototype, test) is a general problem-solving method. The product design process applies those ideas to software and adds stages for engineering handoff, launch measurement and design system maintenance.
What Is the Double Diamond?
The Double Diamond is a design process model from the UK Design Council with four phases: Discover, Define, Develop and Deliver. The first diamond explores and narrows the problem; the second explores and narrows the solution. It now sits within the Design Council’s wider Framework for Innovation.
When Should a Team Create a Design System?
Start a design system once you notice the same components being redesigned repeatedly, or inconsistencies creeping in across screens or teams. Early-stage startups can begin with a small shared component library and grow it. Larger organizations with several products usually benefit from a dedicated design system team.
How Long Does the Product Design Process Take?
For a new feature or MVP, discovery through handoff typically takes 6 to 16 weeks, depending on scope, research depth and team size. Startups often run shorter cycles of 2 to 4 weeks. Iteration after launch is ongoing.
The Short Version
The product design process moves a digital product from an unclear problem to a shipped, measured solution in seven stages: discovery and research, define, ideate, prototype, test, build and handoff, then iterate with a design system. It borrows from the UK Design Council’s Double Diamond and from design thinking as taught by IDEO and Stanford’s d.school, but adds the engineering handoff and post-launch work that software demands.
Scale each stage to the cost of being wrong, keep designers involved through implementation, and loop back whenever testing proves an assumption false. If you lack the people to run a stage well, bring in specialist help for that stage rather than skipping it.
