Creating a persona empathy map for deeper understanding

A persona empathy map turns a research-based persona into a shared view of what a person sees, hears, thinks, feels, says and does in a specific situation. It connects demographic or role details to friction, needs and workarounds, giving teams a common basis for discussing design rather than relying on vague claims about a “typical” user.

The value comes from disciplined evidence. Interview quotes, observed tasks, support requests and usability findings should shape each cell, with assumptions clearly marked. For Australian audiences, that evidence must reflect varied languages, incomes, abilities and access to technology, from busy Sydney commuters to older customers ordering groceries in regional areas.

A collaborative tool can keep the persona, research notes and resulting requirements together. UCDmanager supports personas, use cases, heuristic reviews, usability studies and accessibility evaluation, so an empathy map can become a working reference for the project rather than a one-off workshop artefact. The process works best when the map is tested and revised alongside the research.

Ground the persona in observable evidence

Begin with a defined role and situation. “Shopper”, “commuter” or “small-business owner” is too broad until paired with a goal, such as collecting a prescription, changing a rail booking or reconciling an invoice. Select a use case with enough research coverage to reveal both the intended path and the workarounds people use when the service fails them.

Collect short observations and verbatim excerpts from usability sessions, interviews, surveys and service-desk records. Keep the source and context beside every note so reviewers can distinguish repeated patterns from isolated remarks. A working set of shareable research links can keep supporting material accessible without obscuring the evidence itself.

Capture behaviour, context and emotion

Use the map as a set of evidence prompts. The first pass records what happens in the environment rather than what the team imagines the persona’s motivation to be.

• Sees: forms, labels, prices, signage, confirmation messages and system feedback
• Hears: advice from colleagues, family, service staff or automated prompts
• Does: steps, delays, repeated checks, abandoned tasks and improvised workarounds
• Says: questions, complaints, requests for help and the language used for unmet needs

A second pass connects those observations to the experience of the goal.

• Thinking and feeling: confidence, relief, frustration or anxiety, labelled as hypotheses when not directly stated
• Friction: time, cost, memory demands, uncertainty and inaccessible steps
• Supports: people, devices, prior knowledge and services that make progress possible
• Gains: successful outcomes and signs that the service feels fair, clear and dependable

Keep each statement close to its evidence. Replace “users will be confused” with a sourced observation about a mislabelled field or repeated call to support; specify who encountered it, in which context and how often. This makes the map useful for prioritisation and less vulnerable to stereotypes.

Build the map around an Australian daily journey

Anchor the map to a journey people recognise. For a grocery buyer, that may mean checking specials in a Woolworths or Coles app, changing a click-and-collect order, finding a parking bay and asking a family member to approve a substitution. The service boundary extends beyond the website, so include messages from staff, delivery drivers and payment providers.

Transport creates another revealing context. A Melbourne passenger may move between Myki, trains, trams and buses, while a Sydney commuter balances Opal, station signage, peak-hour crowding and a phone connection that drops in a tunnel. Mapping interruptions shows whether the persona can recover, ask for help or complete the task without spending extra data or time.

Check legal and accessibility obligations without turning the persona into a compliance checklist. The Privacy Act 1988 and Australian Privacy Principles, where applicable, should inform consent and data minimisation. The Australian Consumer Law affects claims, pricing and refunds, while government and state or territory services must be checked against the accessibility requirements that apply to them.

Test the map with real participants

Ask participants to react to the completed map, not merely approve it. During a walkthrough, have them correct inaccurate assumptions and identify missing steps. A participant who says, “I would call my brother before paying”, reveals a confidence or support need that a generic persona may have missed.

Include people with different communication, sensory, mobility and digital access needs, and work with interpreters where language support is appropriate. Avoid treating Australia’s cultural diversity as a single persona attribute; record meaningful differences only when they affect the journey. Revise disputed cells, add confidence levels and note where more evidence is needed before using the map in a decision.

Convert empathy into actionable priorities

Group the mapped needs by consequence rather than by map box. A tiny confusion repeated across every transaction may matter more than a serious but rare issue, while failures affecting access or financial transparency may require immediate attention. Link each priority to the source observation and the persona goal it supports.

Write the selected needs as testable requirements: a clear error message, fewer confirmation steps, a larger tap target or a way to resume an interrupted booking. Add these to relevant use cases and acceptance criteria, then carry them into heuristic evaluation, usability testing and web accessibility conformance work. The map remains valuable because it explains why each requirement matters.

Keep the empathy map alive in the project

Store the persona, map, evidence notes and follow-up actions in the shared project so that product, design, research and engineering see the same reasoning. Give the map an owner and review date, and update it after interviews, major releases or new accessibility findings. Teams seeking advice on project setup can contact the UCDmanager team.

Reuse the map when recruiting participants, drafting a test script and reviewing a new screen. If a participant contradicts an entry, preserve that feedback as evidence and change the claim. Over time, this creates a traceable account of how observed Australian needs shaped design decisions, keeping empathy practical rather than decorative.