User-centred design

What is user-centred design?

User-centred design (UCD) is an approach that keeps the end user's needs, goals and context at the centre of every design decision, from start to finish. The opposite is designing around the business's goals, the technology, or the designer's own taste - all of which can produce something that works for everyone except the person actually using it.

Also known as: user-centred design, user centered design, UCD

Prefer to watch? Watch the recap 1:10

The demo

Same feature - “save this article for later” - designed with a different centre of gravity each time. Switch who it's centred on and watch the experience change. Then notice which one actually serves everyone.

What this demo shows (text version)

The same simple feature - "save this article for later" - is designed three ways, depending on what it's centred on. Centred on the business, it forces a sign-up and pushes a newsletter before it'll save anything, serving a metric at the user's expense. Centred on the technology, it does whatever was easiest to build - a clunky export rather than a real "save". Centred on the user, it just saves the article in one tap, solving their actual task. Switching between them shows how much the centre of gravity changes the result.

That's user-centred design: keeping the end user's needs and goals at the heart of every decision, rather than centring the business, the technology or the designer's taste. It's essentially the same as human-centred design (often broader). And the user-centred version usually serves the business best too - meeting real needs is what builds trust and loyalty.

The question UCD constantly asks is "who is this design centred on?" - and insists the answer be the user. It's easy to drift: to centre the business (maximise this metric), the technology (whatever's easy to build), or the designer's ego (what looks impressive). UCD counters that by grounding decisions in real users - involving them through research, designing for their goals and context, and validating with them iteratively. It overlaps heavily with human-centred design (often used interchangeably; HCD is usually framed as broader, considering everyone affected). The payoff isn't charity: serving the user's real needs is also what builds the trust, satisfaction and loyalty the business actually wants - user-centred and business-centred align far more often than they conflict.

User-centred design puts the end user's needs and goals at the centre of the process, pursued through involving users throughout (research, testing), grounding decisions in their real context, and iterating based on their feedback - rather than designing from assumptions, internal priorities or aesthetics. It's effectively the same iterative loop as human-centred design and ISO 9241-210; the terms are frequently used interchangeably.

The value of naming it is the contrast it draws. Design can be centred on the business (optimising revenue or engagement, sometimes against the user - the slide into dark patterns), on the technology (building what's easy or impressive rather than what's needed), or on the designer (personal taste, ego, novelty over usability). UCD is a discipline that keeps pulling the focus back to the person using the thing, which guards against all three drifts.

The common objection - that user-centred means sacrificing business goals - is mostly false. Genuinely meeting users' needs builds the satisfaction, trust, retention and advocacy that drive business outcomes, so the two usually align (the noble-edge and aesthetic-usability effects reinforce this). Where they genuinely conflict, UCD's stance is to protect the user, both ethically and because a product that fails its users fails the business in the end. Often framed as broader-still human-centred design when wider human impact is considered.