Go Back

Human-Centred Design (HCD)

What is human-centred design?

Human-centred design (HCD) is an approach that puts the people you’re designing for at the centre of the process. You develop a deep understanding of their context, needs, and behaviour, then involve them (and other stakeholders) in defining problems and testing solutions. The result is solutions that work in real life, not just on paper.

Use it when: the problem is complex or the context is unfamiliar, and you want to avoid building something that doesn’t fit how people actually live or work. HCD is the philosophy; design thinking and user research are ways to do it.

Copy/paste checklist (HCD in practice)

Why human-centred design matters

  • Reduces the risk of solving the wrong problem or building something nobody uses.
  • Surfaces needs and constraints that you’d miss without contact with users.
  • Builds empathy and shared understanding across the team.
  • Leads to solutions that are usable, useful, and acceptable in context.

What good HCD includes

Checklist

  • [ ] User contact – Real exposure to users (interviews, observation, testing), not only assumptions.
  • [ ] Problem framed from user perspectiveProblem statement that names who, what, and why from their point of view.
  • [ ] Ideas tested with usersPrototypes or concepts validated with the people you’re designing for.
  • [ ] Iteration – You change direction when evidence suggests it. See iterative design.
  • [ ] Inclusion – Consider accessibility and diversity so the solution works for a range of people.

Common formats

  • Design thinking: Empathise, Define, Ideate, Prototype, Test. A structured HCD process. See design thinking.
  • Participatory design: Users co-create with the team (workshops, co-design sessions). Use when you want direct involvement.
  • Contextual inquiry: Observe and interview users in their environment. Use for deep understanding of context.

Examples

Example (the realistic one)

You’re improving how nurses hand over shifts. Understand: Shadow and interview nurses; empathy map and themes. Define: “Nurses need to hand over critical patient info in under 2 minutes without missing key details; currently they use paper and memory.” Ideate: Brainstorm with nurses and staff; sketch options. Prototype: Paper then digital prototype of a handover checklist. Test: Nurses use it during a simulated handover; you refine. You’ve kept people at the centre at each step.

Common pitfalls

  • No real user contact: “We know our users.” → Do this instead: Schedule user research and testing; involve the people you’re designing for.
  • Problem defined by stakeholders only: The “problem” is what the business wants, not what users need. → Do this instead: Ground the problem statement in user evidence.
  • Testing only internally: No users see the prototype until launch. → Do this instead: Test with real users early and often.
  • One-off engagement: HCD as a single workshop, then back to business as usual. → Do this instead: Make understanding and testing with users part of continuous discovery and feedback loops.
  • HCD vs design thinking: Design thinking is a process that applies HCD (empathise, define, ideate, prototype, test). HCD is the principle; design thinking is one way to do it.
  • HCD vs user-centred design: Often used interchangeably. “Human-centred” can emphasise broader context and systems; “user-centred” often focuses on the product user. Both put people at the centre.
  • HCD vs UX design: UX design is the practice of designing experiences; HCD is the philosophy of involving and understanding people. UX design is typically human-centred.

Next step

Run one HCD cycle on one problem: user research (understand) → problem statement (define) → brainstorming (ideate) → prototype and usability testing (test). Then read Design thinking to deepen the process.