Lesson 1.5Lesson 1.5
Building the persona and the empathy map
Turning a pile of notes into something you can design from
The hookYou've dug below the waterline, shadowed the routine, mapped the day, measured the bodies, read the culture. Your notebook is full — and now you freeze, because you can't hold forty observations in your head at once. The richness that took weeks to gather is now too much to use.
Why synthesis is its own skill
Data without synthesis is paralysis. Gathering and using are different skills. The designer's job at the end of Empathise is to compress the heap into a portrait you can keep in mind while you draw — the convergence half of empathy. The persona answers 'who is this, as a whole human?'; the empathy map answers 'what's going on inside them?' You build the persona to remember the person; the empathy map to understand them.
The persona — a portrait you can hold
A single, vivid, grounded portrait of a key inhabitant, built from real observation. Not a statistic, not an invention. The mind designs far better for a person it can picture: 'the user' invites lazy design; 'Lakshmi, 58, who prays at 6am and whose knees ache on the stairs' invites caring design. A good persona has a line in the inhabitant's own voice that captures the emotional core — so at midnight you can ask 'which layout would Lakshmi feel less like a burden in?' A persona is grounded, not invented: every line earned by something you actually learned.
The empathy map — what's going on inside
Sorts the inhabitant's inner life into four quadrants: says, thinks, feels, does. The power is in the gaps between quadrants, where the real design problems hide. Lakshmi says 'anything is fine, I don't need much'; thinks 'I wish I had a corner to pray, I hope I'm not in the way'; feels like a guest, anxious about being a burden; does pray awkwardly on the bedroom floor and push up painfully on the armrest. A designer who heard only the says column would design nothing for her; the thinks/feels/does columns design her a dignified prayer corner she'd never have asked for.
How the two work together — and hand off
The persona keeps the inhabitant present and human; the empathy map keeps the real problems visible through the gaps. These two artefacts are exactly what Module 2 (Define) needs — you can't define a problem from a heap of notes, you define it from a persona and a map. The gaps you found become the sharp problem statement in the very next lesson.
Build a persona for each distinct user, not one blended average — a joint-family home might need three or four, and the tensions between them (Lakshmi's calm prayer corner vs the teenager's lively evening room, same space) are your hardest, most interesting problems. The most valuable persona is often the one the client didn't ask you to consider — the overlooked inhabitant. And keep these tools living, not decorative: a persona built at the start and never looked at again is empathy theatre; pin it up, consult it at every decision, and revise it when you learn something new.
1. Build one persona for the most overlooked inhabitant of your household — name, age, a one-line quote in their voice, a day in their life, goals, frustrations, and the spatial needs they'd never state (ground every line in real observation). Build their empathy map — says, thinks, feels, does — and circle the single sharpest gap. Write one sentence naming the design problem hiding in that gap; keep it for Lesson 2.1.
Check yourself
3 quick questions — pick an answer to see why.
Q1Why is synthesis described as 'its own skill' at the end of Empathise?
Q2Where does the real design problem hide in an empathy map?
Q3What makes a persona 'grounded, not invented'?
Key terms
- Persona
- A single, vivid, grounded portrait of a key inhabitant — built from real observation, with a quote in their own voice — that keeps the person present while you design.
- Empathy map
- A tool that sorts an inhabitant's inner life into four quadrants — says, thinks, feels, does — whose power lies in the gaps where unstated design problems live.
- The overlooked inhabitant
- The distinct user the client didn't ask the designer to consider — often the most valuable persona to build, such as a grandmother or the household help.
You have Lakshmi, vivid and understood, and a map full of revealing gaps. But 'understand Lakshmi' is not yet a design problem. How do you turn a deeply understood person into one sharp, solvable problem statement?