UX Research

20 May 2025
Human Centered Design HCD
Human-Centered Design (HCD) focuses on real people, not abstract “users.” Calling people “users” can unintentionally dehumanize them. Simon Baron-Cohen highlights how language shapes empathy in Zero Empathy. While we aren’t enemies, labeling people as “users” can reduce our ability to truly understand their needs. Using personas with real names promotes empathy and clarity.
Key Principles of HCD
HCD is about designing for real people in real contexts, not imagined users. The process has four main activities:
- Direct engagement — Interact with real users to understand their needs.
- Observation — Watch users work. Observing behavior often reveals insights that questionnaires can’t.
- Research — Conduct interviews, surveys, or contextual inquiries. Each method has advantages.
- Evaluation — Test solutions with users to spot problems. Alone, evaluation is not enough — it won’t fix poor design.
Context of Use Matters
Understanding how and where people use your system is critical.
Example: Point-of-Sale Systems
- Supermarket: One user per customer, many items, focus on speed and accuracy.
- Cafe or pub: Multiple users share the same system; switching between customers must be fast.
- Lesson: Systems that work in one context often fail in another.
Other contexts—warehouses, factories, outdoor environments — may need different hardware, interfaces, or workflows. Always design for the actual environment, not your office.
HCD Process
The HCD process follows four steps, repeated as needed:
- Research contexts of use — Understand the environment, tasks, and people.
- Gather user requirements — Learn what users need to succeed.
- Design solutions — Produce prototypes, low or high fidelity.
- Evaluate solutions — Test with users and adjust.
Iteration is key. If testing reveals missing contexts or needs, revisit earlier steps.
Why Evaluation Alone Fails
Evaluation is not a fix for poor design.
- Analogy: A factory producing faulty screws won’t improve by only tightening quality checks. You must fix the production process.
- Similarly, usability testing identifies problems but cannot replace user-centered design.
- Example: Ignoring a “troublesome” internal user led to a solution that didn’t meet their needs. Testing after the fact revealed the gap too late.
Best Practices for Effective HCD
- Build multidisciplinary teams — Include diverse skills to solve problems creatively.
- Prototype early — Start with low-fidelity prototypes to test ideas fast.
- Plan for iteration — Allocate time to refine designs based on feedback.
- Educate your team — Ensure everyone understands why HCD matters and how to apply it.
- Integrate HCD into the project cycle — Don’t treat usability as an afterthought.
Summary
HCD is about people, context, and iterative design:
- Design for real humans, not abstract users.
- Observe and research how people actually work.
- Prototype early and test often.
- Iterate until solutions meet real needs.
- Multidisciplinary teams and proper timescales improve outcomes.
Focus on users first, evaluation second. HCD isn’t optional — it’s the key to usable, successful products.