Designing with empathy and human-centred design - understanding the needs and wants of an identified person or group, building empathy as the foundation of the design response, and the difference between latent, expressed and observed needs

What this dot point is asking

Unit 3 is titled "Designing with empathy", and QCAA wants you to understand human-centred design as the approach that puts the needs and wants of an identified person or group at the centre of every decision. You need to explain what empathy means in a design context, how it underpins the explore phase, and how you turn what you learn about a person into design criteria and a justified response. This is the conceptual heart of Unit 3.

The answer

What human-centred design means

Human-centred design (HCD) is an approach that begins and ends with the people who will use the design. Instead of starting from a product idea or a technical capability, the designer starts by understanding a person or group deeply - their goals, frustrations, environment and behaviours - and designs to serve them. The test of a good HCD response is not "is it clever?" but "does it genuinely meet this person's need?"

Why empathy, not sympathy

Empathy is the capacity to understand and share another person's experience from their point of view. It is different from sympathy, which is feeling for someone from the outside. A designer with empathy can describe the problem as the user lives it, which is the only reliable basis for a response that actually helps. Empathy reduces the risk of solving an assumed problem or designing for yourself instead of the user.

Three kinds of need

Empathy work surfaces three layers of need, and strong responses reach the deepest:

• Expressed needs - what the person tells you directly in an interview or survey. Easy to gather, but limited by what people are willing or able to say.
• Observed needs - what you see the person actually do, which often differs from what they say. Observation catches workarounds and habits people do not notice themselves.
• Latent needs - needs the person cannot articulate because they have normalised a problem or cannot imagine an alternative. These are the richest source of innovative design and are usually found by combining interview with observation and immersion.

Empathy methods

In the explore phase you gather empathy data using methods QCAA names explicitly:

• Interviews - open questions that invite stories rather than yes/no answers. "Tell me about the last time you..." reveals far more than "Do you like...".
• Observation - watching the person in their real context, noting what they do, where they hesitate, and what they improvise.
• Experiences and immersion - putting yourself in the user's situation (for example, navigating a space blindfolded to understand a vision-impaired user) to feel the problem directly.

Tools that organise empathy data

• Empathy map - a four-quadrant tool capturing what the user says, thinks, does and feels, which separates surface statements from underlying emotion.
• Persona - a fictional but evidence-based profile of a representative user, giving the design team a concrete person to design for rather than a vague "average user".
• Journey map - a step-by-step trace of the user's experience over time, exposing pain points at each stage.

From empathy to criteria

Empathy data is not the end point - it must be converted into design criteria that guide develop and resolve. A finding such as "the user cannot use the device because both hands are occupied" becomes the criterion "must be operable hands-free". This conversion is the bridge between understanding and designing, and markers look for it explicitly.

Worked example