Designing with empathy and human-centred design (QCE Design Unit 3)
“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”
Designing with empathy means understanding the real needs, wants, feelings and context of an identified person or group, and using that understanding to drive every design decision. It is the core of human-centred design - the approach that designs for people rather than for assumptions. You gather empathy through interviews, observation and immersive experiences, distinguishing expressed needs (what people say), observed needs (what they do) and latent needs (what they cannot articulate). Tools like empathy maps and personas organise the data, which then becomes the design criteria you develop and resolve against. In QCE Design the unbroken line from user need to design feature is what markers reward.
Jump to a section
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
Identified user: an elderly gardener with arthritis who loves growing vegetables but struggles to grip standard tools.
Expressed need (interview): "I want to keep gardening but my hands hurt by mid-morning."
Observed need: she switches the trowel between hands constantly and rests every few minutes - a workaround she did not mention.
Latent need: she has stopped planting deep-rooted crops entirely because the digging is too painful, but she frames this as "just my preference now" rather than a barrier.
Empathy-to-criteria: the tool must require low grip force, distribute load away from the fingers, and enable deeper digging with less effort. These three criteria, traceable to the three need layers, now drive ideation. The latent need - re-enabling deep planting - is where the most original design opportunity sits.
Human-centred design puts the needs of an identified person or group at the centre of every decision. Empathy data comes in three layers - expressed (what they say), observed (what they do) and latent (what they cannot articulate) - and must be converted into design criteria so the explore phase drives develop and resolve.
- Designing for yourself
- Assuming your own preferences match the user's is the classic HCD failure. Empathy data exists precisely to override the designer's assumptions.
- Stopping at expressed needs
- Interviews alone miss observed and latent needs. The richest opportunities are usually in what users do not or cannot say.
- Confusing empathy with sympathy
- Feeling sorry for a user is not the same as understanding their experience well enough to design for it.
- Collecting empathy data and never using it
- If the design criteria do not trace back to the empathy findings, the research was decorative. Markers check the linkage.
- Vague personas
- A persona with no evidence behind it is just a stereotype. Personas must be grounded in real interview and observation data.
Exam-style questions
Questions in the style of QCAA exam questions on this dot point, each with a worked answer. They are written by ExamExplained unless tagged "Past paper"; the year shows the paper a question is modelled on.
Practice8 marksAnalyse the stimulus to explain how a human-centred design approach would change the needs a designer chooses to solve for an elderly user living alone, compared with a designer-led approach. Refer to expressed, observed and latent needs.Show worked answer →
An 8 mark analyse-and-explain answer rewards the contrast between approaches and correct use of the three need types.
A designer-led approach starts from the designer's assumptions and tends to solve only expressed needs (what the user says) or the designer's own preferences. A human-centred approach starts from the user, so it surfaces observed needs (what the user actually does, seen through observation) and latent needs (unspoken or unrecognised needs revealed by empathy work).
For the elderly user, an expressed need might be "larger buttons"; an observed need might be that they avoid a device because the screen glares; a latent need might be the desire to retain independence and dignity. Markers reward defining each need type, tying it to evidence from the stimulus, and concluding that empathy shifts the chosen problem from a surface request toward the deeper, often unspoken, human need.
Practice6 marksEvaluate the claim that building empathy is the foundation of an effective design response. Justify your judgement with reference to the explore phase.Show worked answer →
A 6 mark evaluate answer needs a reasoned judgement, not just agreement.
Argue that empathy is foundational because the explore phase depends on accurately understanding the user; without it, the brief and criteria target the wrong need and every later phase compounds that error. Empathy data (from interview, observation and immersion) is what lets a designer distinguish wants from genuine needs and uncover latent needs.
Temper the judgement: empathy is necessary but not sufficient, because a response also needs sound ideation, prototyping and evaluation. Markers reward a clear position, evidence from the explore phase, and acknowledgement of the limits of empathy alone.