User-Centered Design (UCD)
This post defines User-Centered Design (UCD) — including exam questions and tags.
In a Nutshell
UCD places the needs, goals, and capabilities of end users at the core of the design process through iterative design, evaluation, and feedback cycles.
Definition
UCD follows DIN EN ISO 9241-210 and involves an iterative cycle of:
- Understanding the usage context
- Identifying user requirements
- Developing design solutions (prototypes)
- Evaluating with users
Common methods include personas, user journeys, prototyping (low and high fidelity), and usability testing.
Key Exam Points
- UCD per ISO 9241-210
- Focus on real-world usage contexts
- Iterative process combining research, design, and evaluation
- Personas, prototypes, usability tests (relevant for professional certifications)
- Security: accessible, fault-tolerant interfaces
- ROI: less rework through early feedback
- Documentation of iterations and test results
Core Components
- Target audience analysis
- Usage context
- 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 users
- Refine design
Advantages and Drawbacks
Advantages
- Higher user acceptance
- Early problem detection
- Better usability and accessibility
Drawbacks
- Coordination overhead
- Need for real test participants
Common Exam Questions (Quick Answers)
- What’s the core principle of UCD? Putting the user first.
- Which standard applies? DIN EN ISO 9241-210.
- What are typical methods? Personas, prototyping, usability tests.
Takeaway
Even simple clickable prototypes and short interviews count as UCD and add real value to project documentation.