User-Centered Design (UCD)
This article is a definition guide to User-Centered Design (UCD), complete with exam-relevant points and key concepts.
In a Nutshell
UCD places the needs, goals, and abilities of end users at the centre of the design process through iterative design, evaluation, and feedback cycles.
Core Definition
UCD follows DIN EN ISO 9241-210 and involves these iterative steps:
- Understand the context of use
- Identify user requirements
- Develop design solutions (prototypes)
- Evaluate with users
Common methods include personas, user journeys, prototyping (low and high fidelity), and usability testing.
Exam-Relevant Key Points
- UCD as defined in ISO 9241-210
- Focus on real-world usage contexts
- Iterative cycle of analysis, design, and evaluation
- Personas, prototypes, and usability testing (exam-focused)
- Accessibility: barrier-free, fault-tolerant interfaces
- Cost-effectiveness: less rework through early feedback
- Documentation of iterations and test results
Core Components
- Target audience analysis
- Context of use
- Personas
- Interviews and requirements gathering
- Information architecture
- Prototypes
- Usability testing
- Iterative feedback
- Accessibility
- Documentation
Practical Example
Transit app:
- Interviews with commuters
- Persona "Lisa, 29"
- Clickable Figma prototype
- Usability test with 5 participants
- Refine design
Advantages and Disadvantages
Advantages
- Higher user acceptance
- Early error detection
- Better usability and accessibility
Disadvantages
- Coordination overhead
- Need for actual test participants
Common Exam Questions (with Quick Answers)
- What is the core idea behind UCD? The user at the centre of design.
- Which standard applies? DIN EN ISO 9241-210.
- Typical methods? Personas, prototyping, usability testing.
Key Takeaway
Even simple clickable prototypes and brief interviews count as UCD practice and add real value to project documentation.