The methodology applies to physical and digital products in the same sequence, even though the outputs differ entirely. A physical product team tests a handle’s grip comfort, a packaging design’s shelf legibility, or a medical device’s ease of use under stress. A digital product team tests a checkout flow’s completion rate, an onboarding screen’s clarity, or a dashboard’s information hierarchy. Both teams follow the same underlying discipline: observe real users, define the problem precisely, generate solutions, build something testable, and validate it against actual behavior rather than internal opinion. Figma supports this cycle for digital products. Physical product teams use comparable tools — CAD software, 3D printing, and physical prototyping rigs — to achieve the same testable, iterative loop. WCAG 2.1 accessibility standards inform the digital application of the methodology; universal design principles inform the physical application.

How the User-Centered Design Process Works

Definition. The user-centered design process is an iterative methodology in which user research, problem definition, ideation, prototyping, and testing repeat in cycles until a product demonstrably meets the needs of its intended users. It applies to physical and digital products equally, differing only in the tools used to build and test prototypes at each stage.

What each stage of the process produces

• Research — direct observation, interviews, and contextual inquiry that surface what users actually do, not just what they say they want, for both physical environments and digital workflows
• Definition — a precise problem statement and set of user requirements, often expressed as personas and jobs-to-be-done, that scope what the design needs to solve
• Ideation — a wide exploration of possible solutions before narrowing, using sketching for physical products and wireframing in Figma for digital interfaces
• Prototyping — a testable representation of the solution, ranging from a cardboard mockup or 3D-printed part for physical products to an interactive Figma prototype for digital ones
• Testing and iteration — structured evaluation with real users, producing findings that feed back into definition or ideation rather than concluding the process after one pass

How to Run the User-Centered Design Process in 5 Steps

1. Observe real users in the context where the product will actually be used, before defining any requirements. For physical products, this means contextual inquiry in the kitchen, the hospital ward, or the factory floor where the product will function. For digital products, this means watching users complete tasks in their current tools or workflow, not just asking them to describe their needs in an interview. People are unreliable narrators of their own behavior; direct observation surfaces friction points that self-reported feedback consistently misses.
2. Define the problem with a precise statement grounded in the research findings, not in the client’s or team’s original assumption. A jobs-to-be-done framing — what is the user trying to accomplish, and what is currently getting in the way — produces a sharper brief than a feature list. This stage should produce documented personas, a defined scope, and explicit success criteria that the rest of the process is measured against. Skipping this step in favor of moving straight to solutions is the most common cause of well-executed designs that solve the wrong problem.
3. Generate a wide range of possible solutions before narrowing to one direction. Physical product teams sketch multiple form factors and mechanisms. Digital product teams explore multiple interaction patterns and information architectures in low-fidelity wireframes before committing to a single flow. Premature narrowing — fixating on the first plausible solution — limits the design space before the team has explored whether a better solution exists. Three distinct concept directions, evaluated against the defined success criteria, produce stronger final decisions than one direction refined in isolation.
4. Build a prototype fidelity-matched to the question being tested. Early-stage questions about basic usability and form factor require only low-fidelity prototypes: a cardboard mockup for a physical product, a clickable wireframe for a digital one. Later-stage questions about specific interaction details or material feel require higher-fidelity prototypes closer to the final product. Building high-fidelity prototypes too early wastes time refining details that earlier, cheaper testing might invalidate entirely.
5. Test the prototype with real target users and treat the findings as inputs back into definition or ideation, not as a final approval gate. A usability test that reveals users cannot complete a core task is not a failure of the test — it is the process working as intended, catching a problem before expensive production or development investment. Run this cycle repeatedly until the prototype demonstrably meets the success criteria defined at the start, rather than stopping after a single round of testing regardless of the findings.

Pro tip: Test with users who represent the edges of your target audience, not just the easiest-to-recruit, most enthusiastic participants. A product that works for a power user and an accessibility-dependent user is more robust than one validated only by people similar to the design team. Edge-case users surface problems that mainstream testing consistently misses.

Conclusion

The user-centered design process applies the same five-stage cycle — research, definition, ideation, prototyping, and testing — to physical and digital products alike, differing only in the tools used to build and validate prototypes at each stage. The discipline that makes the process work is the willingness to let user evidence change the direction of the design, repeatedly, rather than treating research as a checkbox before building a predetermined solution. Products developed through a genuine user-centered process consistently perform better on adoption and satisfaction than products designed from internal assumption, because they have been tested against real behavior at every stage rather than only at launch. For companies building a digital product through this methodology, our product discovery service runs the research and definition stages that ground the rest of the process in evidence. For teams ready to move from validated concept to a shipped product, our product design and development services carry the user-centered methodology through ideation, prototyping, and testing to final handoff.