3.4Empathy map & understanding the user
The essentials in 30 seconds
- Empathy map: what the user says, does, thinks, feels, sees, hears — fears and expectations.
- Persona: a reference portrait (what would they think of this solution?) to aim right.
- Ground it in reality: build on interviews and observation — never on invented assumptions.
Running case — Sara discovers the real need
A user says shorten the form. Sara observes instead of executing: he fears making a mistake and losing his entries. With an empathy map and a persona (Yacine, 58, hurried, fears errors), she reveals the implicit need: auto-save + reassurance. The form does not get shorter — it reassures.
Sequel to cases 3.1-3.3 — Sara moves from I think to they need.
1. Understand the person concerned
To solve the right problem, you must deeply understand the person concerned — the heart of the user-centered approach. The empathy map is a visual canvas structuring what you know of a user.
It organizes several dimensions: what they say, do, think, feel, what they see and hear, their fears and expectations. Filling it forces you to truly stand in their shoes.
2. The persona
The persona completes the approach: a portrait of a representative user (name, profile, context, needs, frustrations, goals) that embodies a segment and serves as reference throughout the project (what would our persona think of this solution?).
These tools shift the gaze from what I think is good to what the USER really needs. They surface implicit needs, often more important than expressed ones.
3. Ground it in reality
Caution: these tools must rest on real knowledge of users (observation, interviews), not invented assumptions — otherwise you project your own biases with a false sense of rigor.
Well used, empathy map and personas ensure you design for real people with real needs. That is the difference between a solution that works and one nobody wants.
🔎 Concrete example — The implicit need
What the user says is not always what they need.
Says: I want a shorter form.
Implicit need (observed): they fear making a mistake and losing entries → the real solution is auto-save + reassurance.Result: observation reveals the real need behind the request.
Reflex: meet real users before modeling.
Section vocabulary
- Empathy map
- A canvas structuring what you know of a user (says, does, thinks, feels, sees, hears, fears, expectations).
Simple example: Sara fills in: Yacine says it is too long, thinks I will make a mistake.
What it is not: a sheet filled among colleagues without meeting any user.
Reflex: one map = one real observed user, not an average profile.
- Persona
- A portrait of a representative user (profile, context, needs, frustrations, goals) serving as reference.
Simple example: Yacine, 58, hurried, fears errors, displayed during the project.
What it is not: a first name + a photo + clichés with no data.
Reflex: facing each solution: what would Yacine think of it?
- Empathy
- The ability to understand another's viewpoint and feelings; a key skill of the user-centered approach.
Simple example: Sara restates Yacine's fear before proposing anything.
What it is not: projecting your own comfort (it suits me) onto the user.
Reflex: listen twice as much as you speak in interviews.
- Implicit need
- A real need not directly expressed by the user, often more important than the expressed one.
Simple example: The need for reassurance behind shorter form.
What it is not: taking each request literally.
Reflex: ask why behind each expressed request.
- User-centered approach
- An approach starting from users' real needs rather than the designer's assumptions.
Simple example: Testing auto-save with 3 users before rolling it out.
What it is not: designing for an imaginary user in your own image.
Reflex: no decision without recent user feedback.
In practice — Understanding the user (empathy, personas)
- Fill an empathy map: what the user says, does, thinks, feels; their fears and expectations.
- Create one or more personas (portraits) as reference throughout the project.
- Seek implicit needs, frustrations and deep motivations (beyond the expressed).
- Ground these tools in REAL knowledge (observation, interviews), not assumptions.
Ready-to-say script — empathy interview (1 min)
Tell me about your last visit to reception: what did you do on arrival? What worried you? If everything were perfect, how would it go? — then I restate without proposing a solution.
To ask 3 real users: facts, feelings, ideal — without defending the in-house solution.
Copy-paste template — empathy map + persona
OBSERVED USER (who, when): _______________
SAYS / DOES: _______________
THINKS / FEELS: _______________
SEES / HEARS: _______________
FEARS / EXPECTATIONS: _______________
PERSONA (first name + context + frustration + goal): _______________
IMPLICIT NEED: _______________No direct access
Interview reception staff and reread complaints: 10 verbatims beat zero interviews.
SME in Algeria
Note exact bilingual wording: the reassuring word is not always the form's word.
B2B / internal
Observe the colleague-user in a real situation for 20 min: what they do often contradicts what they say.
Remote
Screen sharing + thinking aloud: seeing hesitations reveals the implicit.
✓ Best practices
- Run a few real interviews: they beat hours of assumptions.
- Seek implicit needs, not just what is said.
- Make your persona a synthesis of observations, not a fiction.
✗ Common pitfalls
- Designing for an imaginary user in your own image.
- Inventing a cliché persona (it formalizes your biases).
- Confusing expressed need and real need.
Key takeaways
- The empathy map structures what you know of the user (says, does, thinks, feels, fears, expectations).
- The persona is a portrait of a user serving as reference throughout the project.
- These tools shift the gaze from what I think to what the USER needs.
- They must rest on real knowledge (interviews), not invented assumptions.
48h challenge — apply tomorrow
Fill 1 empathy map from 2 real observations and name 1 implicit need (template above). Test it with one user.
- I can fill a complete empathy map without inventing.
- I named 1 implicit need distinct from the expressed need.
- My persona rests on reality, not clichés.
Frequently asked questions
Why stand in the user's shoes?
Because the costliest trap is designing for an imaginary user in your image. Real users have other contexts and constraints. Standing in their shoes reveals their real needs, including implicit ones, and avoids solving the wrong problem.
Are personas not just inventions?
Yes, that is a real trap. A cliché invented persona formalizes our biases. It must rest on real knowledge: interviews, observation, complaints, talks with reception. If you have no access to users, treat the persona as hypothetical and validate it through early testing.
Sara fills an empathy map among colleagues, without seeing any user. What is the risk?