TL;DR
AI can help organize user research you already have, but it cannot fabricate evidence about the specific, messy experience of real users — yet that evidence is exactly what makes an empathy map valuable.
The workshop is on the calendar and the data is nowhere. So you ask an AI to think like a frustrated user, and within seconds you have a page full of sticky notes. It looks like a fix, but whose experience is that map actually built on?
What an empathy map is
An empathy map is a team's picture of what it knows about one type of user, laid out in four quadrants — Says, Thinks, Does, Feels — usually built collaboratively in a workshop, stickies up on a wall. Anything that goes on the wall has to come from real stuff: watching a user struggle, hearing them explain it in their own words, reading their support tickets.
AI's 'user' is no one in particular
AI produces something plausible by synthesizing patterns across a lot of text, but it can't describe any one real person. It writes: 'I wish the app would ask me before swapping my items.' A real user says: 'It swapped out my oat milk for a gallon of whole milk and charged me before I even saw the notification.' The first could describe any app; the second is evidence specific to this product.
Where AI belongs
There's a thin line between helping and corrupting. Clustering sticky notes you've already collected, cleaning up language after insights are grounded, summarizing real quotes — that's AI as assistant. Filling gaps in thin research with plausible-sounding filler, inventing a 'typical user' to stand in for interviews you never ran — that's AI as fabrication.
If the data isn't there, stop and go do the research. Generating empathy-map data with AI looks like a shortcut, but it just moves the problem downstream: the team ends up building for users who don't exist, on a map that never required talking to anyone.
Curated from high-quality sources, with concise summaries and key takeaways.
