process & strategy
Human-centred design
What is human-centred design?
Human-centred design (HCD) is an approach that grounds design in a deep understanding of the real people who will be affected by it - their needs, contexts and limitations - and improves the solution through repeated cycles of understanding, designing and evaluating with them. Instead of guessing or designing for yourself, you build around evidence of what people actually need.
Also known as: human-centred design, human centered design, HCD
Prefer to watch?
Watch the recap 1:10
The demo
Two ways to design a product. One guesses, builds, and ships - once. The other loops: understand real people, design, evaluate with them, repeat. Step the loop and watch where each catches its mistakes.
What this demo shows (text version)
Two approaches to designing a product are compared. "Design from assumptions" is a straight line - guess what people want, build it, and ship once - so any misunderstanding of real needs only surfaces at the end, when it's expensive. The "human-centred loop" runs the ISO cycle: understand the real people and their context, specify their requirements, design a solution, then evaluate it with actual users - and repeat. Stepping the loop shows each evaluation catching gaps early and feeding back into the next round.
That's human-centred design: grounding design in real understanding of the people affected and improving through iterative cycles of understanding, designing and evaluating with them. It guards against the central failure of building the wrong thing well. HCD is broader than user-centred design - it considers everyone a design affects - but both share the same loop: real people, involved throughout, evaluated with, and iterated.
Human-centred design means designing from real human needs and evidence, not assumptions or your own preferences - and doing it iteratively. The ISO-defined cycle runs: understand the context and the people, specify their requirements, design solutions, then evaluate against real users - and loop until it works. The core commitments: involve real people throughout, base decisions on understanding their actual context (not imagined users), and iterate. HCD is broader than user-centred design - it considers everyone affected, including non-users and wider impacts - and it guards against the biggest failure in design: building something well-crafted that solves the wrong problem because nobody checked with the humans it's for.
Designing from your own assumptions, you built something neat that missed what people actually needed - and only found out at the end. The human-centred cycle - understand real people, design, evaluate with them, repeat - kept catching the gaps early, so the result fit reality. That's the whole point: ground design in evidence of human need and loop with real people, rather than guessing and hoping.
Human-centred design is formalised in ISO 9241-210 around four iterative activities: understand and specify the context of use (who the people are, their goals, tasks and environment); specify the user requirements; produce design solutions; and evaluate those designs against requirements with real users - repeating the loop until the solution meets needs. Its principles include grounding design in an explicit understanding of users and context, involving users throughout, driving by user-centred evaluation, iterating, and addressing the whole experience.
HCD exists to counter the central risk in design: building the wrong thing well. Designing from assumptions, internal opinion or one's own preferences (the curse of knowledge, false-consensus and empathy gaps all push this way) produces polished solutions to problems users don't have. Anchoring in real understanding and testing each iteration with actual people catches those misfires early, when they're cheap to fix.
Human-centred design is often used interchangeably with user-centred design, but it's usually framed as broader: where UCD focuses on the end users of a specific product, HCD considers all the humans a design affects - including non-users, communities and wider social and ethical impacts - and the whole context. In practice both share the same commitments: understand real people, involve them, evaluate with them, and iterate, rather than designing in a vacuum.