On this page
Scott
Scott

Published on Sep 24, 2024, updated on Nov 02, 2026

User-centered design (UCD) is an iterative approach that uses evidence about people, their tasks and their circumstances to guide design decisions. The team studies the problem, defines needs, explores solutions and evaluates them with likely users. It repeats those activities when the evidence calls for a change.

The practical test is whether a finding changes what you build. In the library-renewal example below, a reader needs to know whether a loan was extended and when the book is due. A collaborative UX design workspace can bring the proposed screens and feedback together; research establishes which problem those screens need to solve.

user centered design

Part 1. What is User-Centered Design?

UCD describes an approach to designing a product or service. UX describes the experience people have with it and the broader discipline that studies and improves that experience. They are related, not competing methods: a UX team can use UCD to decide what to research, prototype and evaluate.

Ultimately, the user-centered design aims to improve the product's usability through iterative design processes. Therefore, users' demands and product accessibility are at the forefront of the UX designers' minds throughout the project.

When developing a new product, designers work closely with consumers to ensure that the result is one they can be proud of. This involves considering the interests, needs, and views on the product of the end-user(s).

Feedback is evidence to interpret alongside observed behavior and service constraints. A request for a new button may point to an unclear existing action. Investigate the underlying task before treating a requested feature as the solution.

Familiar patterns can reduce unnecessary learning, but UCD does not mean preserving every existing habit. A change can be worthwhile when it helps people complete their task more clearly or safely. Explain unfamiliar behavior and evaluate it with the people affected.

what is user centered design

Part 2. The Principles of User-Centered Design (UCD)

The following principles turn a broad commitment to users into decisions a team can inspect:

  • Understand the context. Identify who performs the task, where, with which devices and with what constraints. Include people who need additional support.
  • Use evidence, not a representative imaginary user. Separate interview statements, observed actions and team assumptions.
  • Make requirements testable. Describe the outcome people need, rather than specifying a preferred screen too early.
  • Involve users throughout the work. Study existing behavior and evaluate proposed designs before and after release.
  • Design the complete experience. Consider support, notifications and interrupted tasks as well as the main screen.
  • Iterate with a reason. Change the design in response to a finding, then check the relevant task again.
  • Work across roles. Designers, developers, researchers and service staff need to resolve the same problem together.

Part 3. What’s the Working Process of User-Centered Design?

These five activities are a practical way to organize the work, not a compulsory one-way sequence. Evaluation can send the team back to its assumptions or requirements before it draws another screen.

1. Understanding the consumer and their predicaments

Study how actual or likely users carry out the task today. Ask about a recent attempt and, where appropriate, observe it. Record interruptions, workarounds and the information people use to decide. The GOV.UK guidance on learning user needs distinguishes evidence about users from assumptions held by the team.

2. Defining the needs of the user and the company

This stage defines why the design is of value to both the consumer and the company, as well as the issues it addresses. At this stage, designers and stakeholders are figuring out how to measure commercial success (i.e., projected revenue or ROI) and how to measure success for the consumer.

Having a proper grasp of UX strategy is crucial at this stage because it helps to bridge the gap between user demands and objectives as well as those of the company.

3. Development of innovative design concepts

The next step in the UCD process is to brainstorm solutions to the challenges that have already been identified. This is the main course of design. It includes activities such as storyboarding, journey mapping, wireframing, creating mockups and consumer flows, evaluating various UI components, and establishing a suitable information framework.

Keep the research finding beside the corresponding design decision so a later reviewer can see why the screen changed.

4. Real-world assessment of the product

Evaluate early sketches and prototypes as well as working software. Ask participants to complete realistic tasks and observe what happens. Preference comments can help explain an action, but “I like it” is not proof that someone understood the result. The GOV.UK usability-testing guide recommends tasks that establish a goal without revealing the route.

5. Observe the consumers and product

Whenever a product is introduced, it must be tracked to see if it has the intended effect. In addition to analyzing qualitative indicators, performance monitoring and customer feedback are required.

Observation is an effective method for gathering qualitative information about consumers. It's a means of conducting user research that involves monitoring and interviewing participants as they go about their daily lives. A contextual inquiry is conducted by observing how participants execute their duties and having them describe what they are doing when engaging with a product.

At this stage, typical questions to answer include: What went well? How did our clients react? How can we get better?

It is uncommon for a product's initial design to satisfy all set goals and specifications. In reality, it could take multiple rounds of the UCD process before designers produce a prototype that meets corporate and customer needs. UCD is, therefore, an evolving procedure.

A worked example: renewing a library loan

Suppose a library team is investigating renewal problems. The situation below is an instructional example, not a report of a Pixso customer study. The reader wants to keep a borrowed book for another week without accidentally missing its due date. The library must also respect reservations and explain when renewal is unavailable.

Connect the finding to a requirement

Imagine a session in which a reader selects Renew, sees the loan list again and repeats the action because the date looks unchanged. Record the action first. “The reader did not trust the confirmation” is an interpretation; check what they expected to happen and what they read on screen.

Evidence or questionDesign consequenceWhat to evaluate
The reader repeats renewal after returning to the list.Show a clear outcome beside the affected book, with the updated due date.Can the reader explain whether renewal succeeded and give the new date?
Some books may be reserved by someone else.Give the blocked state a reason and the available next action.Can the reader distinguish a policy restriction from a technical failure?
The connection may fail after submission.Keep the book and task visible; explain whether the outcome is unknown.Does the reader know how to check the current loan rather than repeatedly submit?

Compare two solutions before polishing

Option A shows a confirmation on a separate page. Option B updates the loan card and keeps a persistent message beside the new due date. Build only the screens needed to compare those approaches: the current loan, successful renewal, renewal unavailable and an uncertain connection result. Use realistic book names and dates so the test is about understanding the outcome, not deciphering placeholders.

A neutral task might be: “You need this book for another week. Use the service to find out whether you can keep it, and tell me when it must be returned.” Do not tell the participant to press Renew. Note the route, hesitations, repeated submissions and their explanation of the final state. A small formative study can expose problems; it does not establish a population-wide success rate.

Make the next iteration specific

If readers reach the right screen but still quote the old due date, changing the navigation is unlikely to address the finding. Try grouping the outcome and new date beside the book title. If they never find renewal, inspect the loan-list labels and action placement. After making that change, repeat the relevant task and compare observations under the same conditions.

Agree with the developer how the service checks whether renewal already succeeded, and with library staff how to explain a reservation restriction. Those are service rules, not just interface states. After release, look for repeated-renewal attempts and related support questions alongside task outcomes; do not judge the redesign by button clicks alone.

FAQs About User-Centered Design

Q1. What's the difference between user-centered and human-centered design?

The terms often overlap. Human-centered design emphasizes the people affected by a system; user-centered design commonly focuses on the people using a particular product or service. State the scope of your work instead of assuming one term automatically implies better research.

Q2. What is the difference between design thinking and user-centered design?

Design thinking is a family of approaches to exploring problems and possible solutions. UCD emphasizes understanding users and evaluating designs against their needs. A team can use ideation techniques from design thinking within a user-centered process.

Q3. How is UI UX related to user-centered design?

UI design shapes the controls, content and visual states people interact with. UX work considers the broader experience. UCD provides a way to connect both to evidence about users, rather than making appearance or preference the only basis for a decision.

Turn the findings into a prototype in Pixso

In Pixso, place the loan-list alternatives in one design file and connect the intended actions in a prototype. Put the blocked and connection-error states beside the successful path. Ask reviewers to comment on the exact screen and decision; the file becomes a shared design reference, while the research notes retain the evidence behind it.

pixso

Conclusion

Start with one task where misunderstanding has a visible consequence. Keep the need, proposed change and evaluation question connected. That makes it possible to explain why a design should change and what the team still needs to learn.

A useful UCD cycle ends with a better-informed next decision, not merely a completed set of screens. Return to the evidence whenever a solution fails the task or introduces a new obstacle.

Back to top
Share on X
Share on Facebook