User-Centered Design gets positioned as a UX discipline. It's actually a product risk management strategy.
The pattern it prevents: a team spends months building a product based on assumed user needs, ships it, and discovers that the assumptions were wrong. The features users actually needed weren't built. The features that were built don't get used. Rework is expensive, timeline is blown, and the product is behind where it should be.
UCD interrupts this at the earliest possible stage through three core activities:
User research: interviews, surveys, observations that surface real user needs before any design decisions are made. The output is a clear picture of who the user is, what problem they're trying to solve, and what context they're solving it in. This replaces assumption with evidence.
Prototyping: low-fidelity first, high-fidelity as the design matures. The goal is to test design concepts with real users before implementation, catching usability issues when they cost nothing to fix. Discovering a navigation problem in a Figma prototype takes an hour to fix. Discovering it in production takes a sprint.
Usability testing: real users completing real tasks. Not "do you like this?" but "please complete this task" with observation of where they struggle. This is where you find out what you missed in user research and prototyping.
The ROI on UCD is straightforward: the later in development you discover a usability problem, the more expensive it is to fix. UCD moves discovery as early as possible.
Full guide:
Top comments (0)