{{ p.category }}

{{ t }}

{{ p.title }}

{{ p.excerpt }}

U{{ author.name }} {{ p.readMins }} min read

{{ p.category }}

{{ p.title }}

{{ mo.sub }}

{{ m.tag }}

{{ m.t }}

{{ m.d }}

{{ m.left.t }}

✕{{ x.t }}

{{ m.right.t }}

✓{{ x.t }}

{{ m.big }}{{ m.label }}

{{ x.t }}

{{ m.label }}

✓{{ x.t }}

{{ x.t }}

{{ m.label }}
{{ x.t }}
{{ m.status }}

{{ m.label }}

{{ x.t }}{{ x.n }}

{{ x.t }}

{{ m.label }}{{ m.stepTxt }}

{{ x.t }}

{{ m.btn }}

{{ x.t }}

{{ m.q }}

{{ m.a }}

{{ x }}

{{ k.n }}

{{ k.v }}

{{ m.label }}

{{ m.status }}

{{ m.label }}

{{ st.n }}{{ st.t }}

{{ m.hub }}

{{ nd.t }}

AaAaAaAa

ButtonInput fieldTag

THE SHORT ANSWER

{{ p.answer }}

KEY TAKEAWAYS

✓{{ k }}

RELATED SERVICES

{{ b.t }}

{{ g.t }}{{ g.t }}

{{ g.t }}

{{ b.label }}:{{ b.t }}

{{ c.ini }}

{{ c.t }}

{{ c.d }}

{{ s.n }}

{{ s.t }}

{{ s.d }}

{{ h }}
{{ c.t }}

{{ b.alt }}

{{ g.alt }}

{{ b.title }}

{{ c.t }}

{{ c.s }}

{{ i }}

{{ c.t }}{{ c.s }}

{{ b.caption }}

{{ s.v }}

{{ s.l }}

{{ s.s }}

{{ b.caption }}

{{ b.title }}

{{ b.unit }}

{{ r.l }}{{ r.d }}

{{ b.caption }}

{{ b.title }}

A{{ b.a.t }}

{{ i }}

B{{ b.b.t }}

✓{{ i }}

{{ b.caption }}

{{ b.title }}

{{ t.d }}

{{ t.t }}

{{ b.caption }}

“

{{ b.t }}

{{ b.by }}

{{ b.title }}

{{ r.d }}

{{ r.l }}

{{ b.caption }}

{{ b.title }}

{{ m.n }}

{{ b.lo }}{{ b.hi }}

{{ m.n }}

{{ m.l }}

{{ m.d }}

{{ b.caption }}

{{ b.cs.client }} case study

Case study · {{ b.cs.client }} {{ b.cs.title }} {{ b.cs.text }}

{{ f.v }}{{ f.l }}

View case study →

SOURCES AND FURTHER READING

Frequently asked questions

{{ f.a }}

U

Written by {{ author.name }}

{{ author.role }}

Keep reading

More articles from across design, AI and marketing.

All articles

{{ r.category }} · {{ r.readMins }} min{{ r.title }}

Special Offer

25% Off Your Startup’s First Project

No Obligation
Quick Response
Exclusive for Startups

User-centred design: principles, process and benefits

User-centred design is an approach that bases design on an explicit understanding of users, tasks and environments, involves users throughout, refines designs through evaluation, iterates, addresses the whole experience and uses multidisciplinary teams. Its process moves through understanding context, specifying requirements, producing designs and evaluating them, repeating until the design meets user needs.

What user-centred design is

User-centred design, often shortened to UCD, is an approach to creating products, services and systems in which the needs, goals and limitations of the people who will use them guide every stage of the work. Instead of designing based on assumptions or internal preferences, teams study users, involve them throughout and test designs with them until the result works well in real conditions.

The approach is described in the international standard ISO 9241-210, which uses the term human-centred design. While the standard focuses on interactive systems, its principles apply to websites, apps, physical products and services alike. Our post on user-centred design in web development shows how UCD fits into agile web teams; this guide focuses on the principles and process themselves.

The six principles

Principle	What it means in practice
Explicit understanding of users, tasks and environments	Design is based on research, not assumptions
Users involved throughout	People take part in research, design and testing
Design driven by evaluation	Testing with users shapes decisions
Iterative process	Designs improve through repeated cycles
The whole user experience	Design considers emotions, context and every touchpoint
Multidisciplinary skills and perspectives	Teams combine design, research, engineering and business knowledge

Understanding users, tasks and context

The first principle is that design must be based on a clear understanding of who the users are, what they are trying to achieve and the conditions they work in. This means research: interviews, observation, surveys and analytics. It also means understanding context, such as devices, environments, time pressure and social factors. Our post on usability and context of use explains why context matters so much.

Involving users throughout

User involvement should not be limited to a single round of testing at the end. Users can help define problems, react to early concepts, test prototypes and provide feedback on live products. Involvement can take many forms, from interviews and workshops to beta programmes and ongoing feedback panels. The more often teams hear directly from users, the less likely they are to drift towards designing for themselves.

The four-stage process

Understand and specify the context of use: Research users, tasks, environments and constraints.
Specify user requirements: Translate research into clear needs and success criteria.
Produce design solutions: Create concepts, prototypes and detailed designs.
Evaluate against requirements: Test designs with users and measure against criteria.

The stages repeat. Evaluation often reveals new insights about users or context, which feed back into requirements and designs. Projects continue cycling until the design meets the agreed user requirements.

Even a single quick loop through these stages, with a handful of users, usually improves a design noticeably.

Methods for each stage

Stage	Useful methods
Context of use	Interviews, contextual inquiry, analytics review, stakeholder interviews
Requirements	Personas, journey maps, job stories, success metrics
Design	Sketching, wireframes, prototypes, design systems
Evaluation	Usability testing, A/B testing, surveys, accessibility audits

Our guide to 15 user research methods describes many of these techniques in detail.

Designing the whole experience

UCD looks beyond individual screens to the full experience: how people first hear about a product, how they learn to use it, how they get help, how they feel along the way and how the product fits into their lives. A beautifully designed app can still disappoint if support is unhelpful or onboarding is confusing. Mapping the full journey helps teams see and improve every touchpoint.

A short example

Imagine a government agency redesigning an online licence application. Research shows that many applicants are small business owners completing the form on their phones between jobs, often in Arabic, and that they abandon the process when asked for documents they do not have ready. Using these insights, the team adds a checklist of required documents before the form starts, saves progress automatically, offers a fully designed Arabic version and tests prototypes with real applicants. Completion rates rise and support calls fall, because the design now fits the people and context it serves.

Benefits of user-centred design

Higher adoption: Products that meet real needs are more likely to be used.
Lower development costs: Problems found early are cheaper to fix.
Reduced risk: Testing assumptions avoids building the wrong thing.
Better accessibility: Designing with diverse users widens reach.
Fewer support requests: Clearer products need less help.
Stronger loyalty: People return to products that work well for them.

Common challenges

Limited time or budget for research
Stakeholders preferring opinions over evidence
Difficulty recruiting representative users
Research findings not reaching decision-makers
Treating UCD as a one-off phase rather than ongoing practice

Most challenges can be eased by starting small, sharing findings vividly and showing the value of early user involvement through results. Our post on sharing research insights offers practical tips.

Frequently asked questions

What are the principles of user-centred design?

Understanding users and context, involving users throughout, evaluation-driven design, iteration, designing the whole experience and multidisciplinary teams.

What is the user-centred design process?

Understanding context, specifying requirements, producing designs and evaluating them, repeated until user needs are met.

Is user-centred design the same as human-centred design?

They are closely related. ISO 9241-210 uses "human-centred" to include all stakeholders, not only end users.

Does UCD work with agile?

Yes. Research and evaluation can be built into each sprint so designs improve continuously.

How much research does user-centred design need?

Enough to make informed decisions. Even a few interviews and a short usability test can change a design for the better.

Who should be on a user-centred design team?

Designers, researchers, engineers, product managers and people who understand the business and users, such as support or operations staff.

Related articles