A design philosophy and iterative process that keeps end-user needs, behaviors, and constraints at the center of every stage — from research through delivery. UCD involves users at multiple points rather than designing based on assumptions, and treats early feedback as essential data rather than optional input.
Common contexts
- Establishing a UCD process for a team that has historically shipped based on stakeholder requirements alone
- Justifying the cost of three research touchpoints to a product manager by framing them as risk reduction
- Restructuring a project timeline to insert user testing between wireframe and high-fidelity stages
Use when
Apply user-centered design as the default process for any product serving users whose behaviors, contexts, and mental models you don't already know with high confidence — which is almost every product. The cost of a few research touchpoints is trivially small compared to the cost of shipping to the wrong assumptions.
Avoid when
Don't treat UCD as a rigid checklist of phases that must be completed sequentially — in fast-moving startup environments or late-stage critical fixes, the spirit of UCD (testing assumptions early and often) matters more than executing every formal activity in the correct order.
The teams that most resist user-centered design are often the ones who most believe they already understand their users — and that confidence is exactly what makes the first round of usability testing so instructive.
Real-world examples
- ISO 9241-210 formalised user-centred design as an international standard in 2010, requiring organisations to demonstrate iterative user involvement — a standard that Apple, Google, and GOV.UK all cite as a framework for their design processes.
- IDEO's development of the Palm V PDA used UCD methods to involve 50 target users throughout a 9-month design process, producing a device that sold 1 million units in its first year versus the complex Palm III it replaced.
- The NHS's '111' telephone triage service was redesigned using UCD after patient safety incidents; involving patients in co-design sessions identified that the scripted questions were interpreted differently by callers in distress versus the clinical intent.