An empathy map is a UX research tool that helps a team visualize what a user thinks, feels, says, and does in relation to a specific experience or problem — usually organized into four quadrants that force you to separate what someone actually said out loud from what they were probably feeling underneath it, and what they did versus what was going on in their head while doing it. It's built from real research: interviews, observations, usability testing sessions, not assumptions dressed up as insight. The whole point is to take everything scattered across notes and recordings and compress it into something a whole team can look at and immediately understand.
What distinguishes the empathy map from other activities carried out during workshops is the fact that it reveals the inconsistencies between what users say and what they mean by it. Namely, people may say that the checkout flow of the website is "fine" and their actions may show the hesitation regarding the payment process. Or, users may claim that "they don't mind" filling out the form, but then quit it halfway through.
In the case of businesses, this value occurs early in the process, when it can be used the most cost-effectively. Empathy mapping during discovery, before any wireframing or interface design takes place, makes product decisions align with actual user frustration and motivations instead of the assumptions that "the users probably want" something. This prevents the team from making a mistake that is fairly common and expensive at the same time – weeks spent on UI UX design of a feature solving a problem that does not exist for the user or misunderstanding his or her emotional reasons for doing things in the certain way.
There is another subtle aspect of the process that helps greatly to save time and resources. The point is that the designers, developers, product managers, and other stakeholders usually have their own vision of the user and his or her needs. An empathy map based on research instead of opinions allows all the participants to be on the same page without useless discussions and disagreements which are often caused by the fact that five people are imagining five different users.
For enterprise teams developing complex products like banking apps, internal tools, and multi-step retail processes, this is especially relevant because the emotional state of the user at every point (confusion, hesitation, frustration, relief) might explain the drop-off rates better than any usability metrics.
