In simple terms
A friendly intro before the formal notes — no formulas yet.
Designing With, Not Just For, People
User-centred design (UCD) is a design approach that puts the user's needs, wants, and limitations at the centre of every stage of the design process. The goal is to create a product that is highly usable and provides a great experience for the person who will actually be using it.
Imagine you're designing a custom backpack for a friend who is a keen hiker. Instead of just guessing what they need, you'd go hiking with them. You'd observe how they currently pack, what they struggle to reach, and what they complain about on the trail. You'd then make a rough prototype, let them test it on a short walk, and use their feedback to improve it. This continuous cycle of observing, creating, and testing with your friend is the essence of UCD.
- 1
Identify Users & Context: Begin by researching the target user population. Understand their goals, tasks, and the environment in which they will use the product.
- 2
Specify User Requirements: Translate the research findings into concrete design requirements. Develop tools like personas and scenarios to keep the design team focused on the user's needs.
- 3
Produce Design Solutions: Create a range of design solutions, starting with low-fidelity sketches and progressing to more detailed, interactive prototypes.
- 4
Evaluate Against Requirements: Test the prototypes with actual users to gather qualitative and quantitative feedback. Use this feedback to refine the design, iterating through the cycle until the user's goals are met effectively.
Explore the concept
Use the live diagram and synced steps — play it or tap a step card to walk through.
Full topic notes
Formal explanation with the rigour you need for the exam.
The Core Principles of UCD
User Focus: The user is the central concern from the very beginning and throughout the entire process. Design decisions are constantly evaluated against user requirements.
Empirical Measurement: Designs are tested with real users early and often. This involves collecting qualitative data (e.g., opinions, frustrations) and quantitative data (e.g., task completion times, error rates).
Iterative Design: The design process is cyclical. It's a loop of designing, prototyping, and testing. Feedback from one cycle is used to inform the next, leading to progressive refinement.
Holistic Experience: UCD considers the entire user experience, including usability, accessibility, desirability, and the context in which the product is used. It's not just about the interface, but the whole journey.
Essential UCD Tools: Personas and Scenarios
To maintain a focus on the user, designers employ specific tools to synthesise their research. A persona is a detailed, semi-fictional profile of a key user type. It's not just a demographic summary; it includes a name, a photo, goals, motivations, and frustrations. For example, a persona for a new banking app might be 'Priya, a 24-year-old freelance graphic designer who needs to track invoices and save for a house deposit but finds traditional banking apps confusing and time-consuming.' This brings the user to life for the design team.
A scenario builds on a persona. It's a narrative that describes how a persona would interact with the product in a specific context to achieve a goal. For Priya, a scenario might be: 'Priya has just finished a project and receives a payment. She wants to quickly log the income against an invoice, set aside 20% for tax, and move the rest into her savings account, all while on the bus home.' This helps designers test the logic and flow of their design against a realistic situation.
The Iterative UCD Process (ISO 9241-210)
The international standard ISO 9241-210 outlines a framework for human-centred design. It is not a rigid, linear process but an iterative cycle of four main activities. The process begins with understanding the context and ends with evaluation, but the findings from evaluation feed back into the understanding and refinement of the design, creating a loop that continues until the user's needs are met.
1. Understand and specify the context of use: Who are the users? What are their tasks? What equipment and environment are involved?
2. Specify the user requirements: What are the user's goals? What must the product do to meet these goals and fit the context of use?
3. Produce design solutions: Develop concepts, sketches, and prototypes that aim to meet these specified requirements.
4. Evaluate the design: Test the prototypes with real users against the context and requirements. This is the most critical step for gathering feedback for the next iteration.
In Paper 3, questions on UCD often ask you to 'discuss', 'evaluate' or 'explain' the process in relation to a specific product scenario. Avoid just listing the steps. Instead, apply each step to the given context. For example, when discussing 'evaluation' for a new children's toy, mention specific methods like observing children playing with a prototype and interviewing their parents.
Worked examples
See the formulas applied — reveal one step at a time, like the exam.
A company is developing a new smart water bottle designed to help office workers stay hydrated. Create a primary persona for this product. Justify your choices. [6 marks]
- 1
A well-defined persona is crucial for guiding the design of the smart water bottle.
Explain how the UCD process could be applied to the development of a mobile app that helps elderly users manage their daily medication schedule. [8 marks]
- 1
Applying the UCD process would ensure the app is effective and accessible for its specific user population.
How it all connects
The big idea sits in the middle — tap a linked idea to explore the link.
Tap a linked idea to see how it connects back to the main topic — that connection is what examiners reward.
Glossary
Try to recall each definition before you reveal it.
Quick check
Answer in your head first — then tap to check. No pressure.
Revision flashcards
Flip the card. Test yourself before the exam.
What is User-Centred Design (UCD)?
An iterative design process philosophy in which the needs, wants, and limitations of end users of a product, service or process are given extensive attention at each stage of the design process.
Key takeaways
Review these before you close the topic — retrieval beats re-reading.
- ✓
User Focus: The user is the central concern from the very beginning and throughout the entire process. Design decisions are constantly evaluated against user requirements.
- ✓
Empirical Measurement: Designs are tested with real users early and often. This involves collecting qualitative data (e.g., opinions, frustrations) and quantitative data (e.g., task completion times, error rates).
- ✓
Iterative Design: The design process is cyclical. It's a loop of designing, prototyping, and testing. Feedback from one cycle is used to inform the next, leading to progressive refinement.
- ✓
Holistic Experience: UCD considers the entire user experience, including usability, accessibility, desirability, and the context in which the product is used. It's not just about the interface, but the whole journey.
Practice — then mark it
The whole point: a real Cambridge question, marked mark-by-mark.
Test your knowledge on User-Centred Design
Test your knowledge on User-Centred Design
Extra simulations & links
PhET, GeoGebra and other curated tools — open in a new tab.
Frequently asked
Checkpoint
One marked question is worth ten re-reads — close the loop before you move on.
Reading it isn’t knowing it — prove it.
Before you move on: do Test your knowledge on User-Centred Design on paper, snap a photo, and get examiner-style feedback on exactly where you win and lose marks.