User-Centered Design (UCD)
This article is a definition of terms for User-Centered Design (UCD) – including exam questions and tags.
In a Nutshell
UCD places the needs, goals, and abilities of end users at the center – through iterative design, evaluation, and feedback.
Compact Technical Description
UCD follows DIN EN ISO 9241-210 and comprises iteratively:
- Understanding usage contexts
- Deriving requirements
- Developing design solutions (prototypes)
- Evaluation with users
Methods: Personas, User Journeys, Prototyping (low/high fidelity), Usability Tests.
Exam-Relevant Key Points
- UCD according to ISO 9241-210
- Focus on real usage contexts
- Iterative process of analysis, design, evaluation
- Personas, prototypes, usability tests (IHK-relevant)
- Security: accessible, error-tolerant interfaces
- Cost-effectiveness: less rework through early feedback
- Documentation of iterations/test results
Core Components
- Target audience analysis
- Usage context
- Personas
- Interviews/Requirements gathering
- Information architecture
- Prototypes
- Usability tests
- Iterative feedback
- Accessibility
- Documentation
Practical Example
Route planning app:
- Interviews with commuters
- Persona "Lisa, 29"
- clickable Figma prototype
- Usability test with 5 people
- Adjust design
Advantages and Disadvantages
Advantages
- Higher acceptance
- Early error detection
- Better usability/accessibility
Disadvantages
- Coordination effort
- Real test subjects needed
Typical Exam Questions (with Short Answer)
- Basic idea of UCD? Human at the center.
- Which standard? DIN EN ISO 9241-210.
- Typical methods? Personas, Prototyping, Usability Tests.
Free Answer
Even simple click prototypes and brief interviews count as UCD and are valuable in project documentation.