How do personas and empathy maps turn raw empathy data into a shared, usable picture of the person a designer is designing for?
Synthesising empathy data into personas and empathy maps - what a persona and an empathy map are, how they are built from interview, observation and immersion data, what each captures (says, thinks, does, feels), and how they keep the identified user present through develop and resolve
A focused answer to the QCE Design Unit 3 subject matter on personas and empathy maps. What each tool is, how they are built from interview, observation and immersion data, what an empathy map captures, and how they keep the identified user present through develop and resolve, with a worked example.
Reviewed by: AI editorial process; not yet individually human-reviewed
Have a quick question? Jump to the Q&A page
What this dot point is asking
QCAA wants you to be able to synthesise the empathy data you gathered into tools that make the identified person concrete and keep them at the centre of every later decision. Personas and empathy maps are the two main synthesis tools. This dot point asks you to know what each is, how to build it from real data, and how it earns its place in the folio. Marks come from synthesis grounded in evidence, not invented characters or decorative templates.
The answer
From data to synthesis
Empathy research produces a pile of findings - interview quotes, observation notes, immersion reflections. On their own they are hard to act on. Synthesis tools compress that pile into a clear, shared picture of the person. Personas and empathy maps are the two QCAA-relevant tools for this, and they complement each other: the persona is the profile, the empathy map is the structured breakdown behind it.
The persona
A persona is a short profile of the identified user, written as if describing a real person. A useful persona captures:
- Who they are - a name and enough context to make them feel real (their situation, not stereotypes).
- Goals - what they are trying to achieve.
- Needs - the evidenced requirements from your analysis.
- Frustrations - the pain points your research surfaced.
- Context - where, when and how the relevant activity happens.
In Unit 3 you often design for a single identified person, so the persona is a faithful synthesis of that one individual rather than a fictional average. Every line should be defensible against a piece of data.
The empathy map
An empathy map is a structured grid that sorts what you learned into four quadrants:
- Says - direct quotes and stated views, from interview.
- Thinks - inferred beliefs and concerns, what occupies the person even if unspoken.
- Does - observed actions and behaviours, from observation.
- Feels - emotions, from interview tone, observation and immersion.
The power of the map is in the gaps between quadrants. When what a person says differs from what they do, or what they feel differs from what they say, you have found a tension that points to a latent need. The map makes those tensions visible at a glance.
How they are built from real data
Both tools must be built from the empathy data, not invented:
- Gather findings from interview, observation and immersion.
- Sort each finding into the empathy map quadrant it belongs in.
- Read across the quadrants for tensions and patterns.
- Distil the patterns into the persona's goals, needs and frustrations.
Each claim in the persona should be traceable to a finding in the map, and each finding in the map to a piece of research. That chain is what makes the synthesis defensible.
Why they matter through develop and resolve
The danger in develop and resolve is drift - the designer follows what is technically interesting rather than what the user needs. A persona pinned to the work is a constant check: would this feature serve the person in the profile. The empathy map is the evidence base the design criteria were drawn from, so returning to it during evaluation re-grounds the justification in the user. These tools are what keep human-centred design human-centred across the whole process.