Empathy Map vs Value Proposition Canvas
Both tools live on the customer side of product work, close enough that teams often pick one at random. The distinction: an empathy map synthesises raw research — what one person says, thinks, does, and feels — while the Value Proposition Canvas structures the conclusion — the jobs, pains, and gains of a segment, matched against what you offer.
One is upstream of the other. The empathy map has no product side at all; it exists to keep your evidence honest before you touch your offer. The VPC assumes you already know the customer's jobs and pains — and if you have not done the research, it will happily structure your imagination instead.
| Empathy Map | Value Proposition | |
|---|---|---|
| Input | Raw interviews and observation | Known jobs, pains, and gains |
| Includes your product | No — customer only | Yes — offer mapped against customer |
| Unit | One person (then find patterns) | One segment |
| Output | Shared picture of who the user is | A value proposition and feature shortlist |
| Key risk | Filling it from imagination | Product side written first, customer side bent to fit |
| Author | Dave Gray, XPLANE | Osterwalder et al. (2014) |
Use the Empathy Map when…
- You have interview notes rotting in a document
- The team argues about users from memory
- You need the customer's own vocabulary for copy and positioning
- Before writing any value proposition at all
Use the Value Proposition when…
- The research is done and the question is what to build
- A technically good product is not selling
- You need to cut features that map to no real pain
- Writing the landing page — pairings become copy directly
Using them together
Empathy maps first, one per interviewee; the pains and gains that recur across several maps become the customer profile of the Value Proposition Canvas, in the users' own words. Then — and only then — map your product against it. This exact sequence is the 'Understand your customer' playbook here.
The verdict
Order, not choice. Empathy map to digest the research, VPC to design against it. Using the VPC without the research step produces the most dangerous artefact in product work: a confident document describing customers who do not exist.