Introduction
The idea that products should be designed around the people who use them sounds too obvious to need a name. It got one because the default was the opposite: systems designed around technology, business logic, and the assumptions of their makers, with users expected to adapt. User-centred design is the discipline that inverts that default, placing users' needs, abilities, and contexts at the centre of every design decision and validating the design against real people at every stage. This article covers what UCD requires, its principles and process, and the research that makes "user-centred" a practice rather than a slogan.
What is User-Centred Design?
User-centred design (UCD) is an iterative design approach in which the needs, goals, limitations, and contexts of the people who will use a product drive every stage of its development, and in which designs are evaluated against real users repeatedly rather than validated once at the end. The approach was named and popularised in the 1980s (Donald Norman's work at UC San Diego and his book The Design of Everyday Things being the most influential statement), and it has since been codified as an international standard: ISO 9241-210 defines human-centred design for interactive systems through a set of principles that read as a checklist for the whole discipline. The design is based on an explicit understanding of users, tasks, and environments; users are involved throughout; the design is driven and refined by user-centred evaluation; the process is iterative; the design addresses the whole user experience; and the team includes multidisciplinary skills and perspectives.
The Process
UCD's standard cycle has four activities that loop until the design meets its goals. Understand the context of use: who the users are, what they're trying to accomplish, and under what conditions, through user research methods from interviews to field study. Specify user requirements: the needs and goals the design must serve, expressed in terms users would recognise (often via personas, scenarios, and jobs). Produce design solutions: from sketches to prototypes to working software, at rising fidelity. Evaluate against requirements: usability testing and other empirical checks with representative users, whose findings send the cycle round again. The word iterative is doing the work: a single round of research at the start followed by a single test at the end is user-informed design, not user-centred.
What Makes It Real
1. Actual users, not proxies.
Stakeholders, colleagues, and the team's own intuitions are not users; the discipline lives or dies on recruiting the real audience and watching them.
2. Evaluation early and often.
Cheap tests of low-fidelity prototypes catch problems when changing them costs an afternoon. Fast, repeatable studies (an unmoderated prototype test with screened participants, run and re-run as a Ballpark study across iterations) are what make "often" affordable.
3. Measurable goals.
Usability objectives stated in advance (task success, time, error rates, satisfaction via standardised scales) so that "good enough to ship" is a criterion rather than a feeling, tracked as UX metrics.
4. The whole experience in scope.
Onboarding, errors, help, and the surrounding service, not just the happy path on the main screen; accessibility is a user-centredness test the process either passes or fails.
5. Research findings that reach decisions.
UCD fails quietly when studies happen but the roadmap doesn't move; the process includes the organisational plumbing that connects evidence to choices.
UCD and Its Neighbours
Design thinking shares the human-centred core and adds problem-reframing and ideation emphasis; UCD is more process-defined and evaluation-heavy. Agile methods share the iteration and sometimes crowd out the research; the reconciliation is research that runs a step ahead of delivery. Iterative research is UCD's evaluative engine, isolated. And "user-centred" has a mature critique of its own: designing for the individual user can neglect the wider systems, communities, and non-users a product affects, which is why later frameworks widen the circle to stakeholders and society. The critique is right and the core survives it: the people affected by a design should shape it, and the evidence should come from them.
The Takeaway
User-centred design puts real users' needs and contexts at the heart of every decision, and checks the design against real users at every stage, in a loop that runs until the evidence says stop. Understand, specify, design, evaluate, repeat; with actual users, early and often, against measurable goals, across the whole experience, and with findings that reach the roadmap. The name states the obvious. The practice is what makes it true.
Further reading
For principles and process:
Articles:
1. User-Centered Design - Interaction Design Foundation
The approach, its ISO-standard principles, and the iterative process, with practical guidance.
Books:
1. The Design of Everyday Things - Don Norman
The foundational argument that failures blamed on users are failures of design, and the principles that follow.