Most empathy maps stop at understanding.. and that's where most of the value gets left on the table.
The standard version gives you what someone says, thinks, feels, does, and you come out of a round of interviews with a richer picture of the person you're designing for.
Thats genuinely useful, especially in change work where most teams skip the listening entirely.
Nevertheless, useful and actionable arent the same thing.
When a team lead tells you that people find reasons to go back to the old way... thats not just a theme to cluster on a wall, no... thats a diagnostic signal. It could be a belief that the new approach doesnt actually work, or a norm where enough people around them are quietly doing the same thing that it reads as acceptable, or a system that just makes the old way faster.
You can see that all these are completely different problems, completely different responses.
The version you can use is built around the target behavior in the center, not improve collaboration or adopt the new process.. but what someone actually needs to do, and in what context.
Specific enough to be observable and measurable.
Then you have Know part, which covers whether they actually have the knowledge and skills to do it.
The Think part covers intentions, goals and so on....
The Feel part covers the emotional side underneath the conscious reasoning.
The See part, which in my opinion is the most overlooked piece cover the environment, whether theres time, resources or whether the culture and norms around them support the behavior.
Each quadrant is a different category of a possible barrier, and once you can classify what you are hearing, you can start matching it to responses that actually address the right thing, instead of defaulting to another comms thing or a training that doesnt touch the real problem.
The empathy map doesnt need replacing, it just needs a refresh.. one that turns what people tell you into something you can actually act on.