“Should we use the Value Proposition Canvas, an Empathy Map, or Jobs to Be Done?” I hear this question in roughly one out of every three workshops I run. The team has read about all three frameworks. They have seen Medium articles arguing each one is superior. And now they are stuck comparing tools instead of understanding customers.
After 100+ sessions over 10 years with the Value Proposition Canvas, and plenty of work with Empathy Maps and JTBD, my answer is always the same: these are not competing tools. They answer different questions at different stages. The real question is not which framework is best. It is which one matches where your team is right now.
This is the diagnostic approach I use with clients. Not “one is better,” but “here is how I decide.”
Request a Strategy Call about your Value Proposition
In 30 minutes, I'll pinpoint where your value proposition connects with what customers need, and where it doesn't. Or book a workshop where your team builds customer profiles from evidence, not assumptions.
What each framework actually does (in 60 seconds)
Before comparing, let me be precise about what each tool is designed for. Most confusion starts with vague descriptions.
Value Proposition Canvas
Designed by Alex Osterwalder, the VPC has two sides. The Customer Profile captures jobs, pains, and gains. The Value Map captures your products/services, pain relievers, and gain creators. The entire point is to map what customers need against what you offer and find fit or gaps.
It is a decision tool. You fill it in to decide where your value proposition should focus.
Empathy Map
Originally created by Dave Gray and updated by XPLANE, the Empathy Map captures what a customer thinks and feels, sees, hears, says and does, plus their pains and gains. It is broader and less structured than the VPC. Its purpose is not product-market fit. Its purpose is building shared empathy for a customer segment within your team.
It is an exploration tool. You fill it in to build understanding before making decisions.
Jobs to Be Done
JTBD, rooted in the work of Clayton Christensen, focuses on the “job” a customer is “hiring” a product to do. It goes deeper than task-level jobs. It asks: why do customers switch from one solution to another? What is the functional, social, and emotional progress they are trying to make? What are the push and pull forces, and what anxieties hold them back?
It is a theory and a research method. You use it to understand competitive switching dynamics at the decision level.
The real differences: what each tool does well (and where it falls short)
Here is a comparison I give to teams before we pick a framework. No tool is perfect. Each has blind spots.
| Dimension | Value Proposition Canvas | Empathy Map | Jobs to Be Done |
|---|---|---|---|
| Primary question | Does our offer match what the customer needs? | What is this customer’s world like? | Why do customers switch solutions? |
| Best input | Customer interviews, observation, data | Team knowledge, early interviews, field research | Switching interviews, purchase timeline analysis |
| Structure level | High (six defined fields) | Medium (six quadrants, open-ended) | Low (narrative/theory-driven) |
| Output | Fit/gap analysis for your value proposition | Shared team empathy, hypothesis generation | Causal understanding of switching behavior |
| Blind spot | Assumes you already know enough about the customer to categorize their jobs, pains, gains | Does not connect to your value proposition directly | Does not produce a structured profile you can design against |
| Team skill needed | Moderate: needs facilitation to avoid listing features | Low: accessible to any team member | High: needs trained interviewers and analysis skills |
The pattern I see: teams that jump straight to the VPC without enough customer knowledge produce a fiction canvas. Teams that stay in Empathy Map territory never connect insights to product decisions. Teams that do JTBD research but skip the VPC end up with great understanding and no actionable framework.
My diagnostic: how I decide which tool to use with a client
Over 100+ sessions, I have developed a simple diagnostic. I ask the team three questions before we start, and the answers determine which framework we begin with.
Question 1: How much do you know about your customer?
If the team has done fewer than five customer interviews and cannot describe a typical customer’s week in specific detail, we start with the Empathy Map. Not because it is better. Because the VPC requires a level of specificity that this team does not have yet. Putting them in front of a VPC will produce guesses dressed up as insights.
If the team has real customer data, interview transcripts, support tickets, lost-deal analyses, or direct customer access, we go straight to the VPC. They have what they need to fill it in properly.
Question 2: What decision are you trying to make?
“We need to understand who our customer really is.” That is Empathy Map territory.
“We need to figure out why customers are choosing our competitor.” That is JTBD territory.
“We need to design (or redesign) our value proposition.” That is VPC territory.
“We need to understand why our current proposition is not landing.” That starts with JTBD (to understand switching) and then moves to the VPC (to redesign the offer).
Question 3: What is your team’s experience with customer frameworks?
For teams new to structured customer thinking, the Empathy Map is the easiest entry point. I have seen cross-functional groups of engineers and finance people produce useful Empathy Maps in 45 minutes. The same team with a VPC often stalls because they confuse jobs with features, gains with “no pains,” and the whole thing becomes an internal debate.
For experienced teams, the VPC is more efficient because it produces directly actionable output.
When to use which: five scenarios from actual client work
Theory is useful. Practice is better. Here are five situations from my work where the framework choice made a measurable difference.
Scenario 1: Manufacturing company entering a new market segment
A manufacturing company with €40M revenue wanted to move from commodity components into engineered solutions for the food processing industry. They knew their current customers well. They knew almost nothing about food processing.
Choice: Empathy Map first, then VPC.
We started with Empathy Maps based on three exploratory interviews with food processing plant managers. The maps exposed how much the team was projecting their own assumptions. “We thought they cared about tolerances. They care about cleaning validation and audit trails.” After two more rounds of interviews, we moved to the VPC with real data. The resulting value proposition focused on documentation and traceability, not precision, which is not what the engineering team would have built on their own.
Scenario 2: B2B SaaS company losing deals to a competitor
A software company was losing 40% of late-stage deals to one specific competitor. The sales team blamed pricing. Leadership suspected something else.
Choice: JTBD interviews first, then VPC.
I ran eight JTBD-style switching interviews with customers who had chosen the competitor. The pattern was clear: the competitor offered a 2-week implementation, while my client’s implementation took 12 weeks. The “job” these buyers were hiring the software to do was not “manage production data.” It was “show results to the board within one quarter so the digital transformation budget gets renewed.” Implementation speed was the switching trigger. Pricing was a secondary rationalization. We used that insight to rebuild the VPC around time-to-value rather than feature richness.
Scenario 3: Innovation team validating a new product concept
A corporate innovation team had a concept for predictive quality monitoring. Early stage, lots of assumptions, no paying customers yet.
Choice: VPC as assumption map, then test.
Here we used the VPC differently. Not to capture known customer realities, but to make assumptions explicit. We filled in the canvas with the team’s best guesses, then marked every item as “assumption” or “evidence.” Out of 23 items on the customer profile, 19 were assumptions. That is not a value proposition. That is a testing plan. We designed experiments to validate the top five assumptions before investing further in development.
Scenario 4: Product team redesigning an existing B2B offering
An established company with 200+ customers and ten years of market data wanted to reposition their core product against new market entrants.
Choice: Straight to VPC.
They had the data. Sales team had direct customer relationships. Support had years of ticket history. We did not need an Empathy Map to build understanding. We went directly into customer profiles per stakeholder role (procurement, operations, management) and compared those profiles against the current value proposition. The gaps were specific: the product delivered on functional pains but completely ignored the social job of “help me justify this purchase internally with a business case my CFO will accept.”
Scenario 5: Cross-functional team with no shared customer understanding
An R&D-heavy organization where engineers, product managers, and sales each had a different picture of “the customer.” Three different mental models, three different sets of priorities.
Choice: Empathy Map as alignment exercise.
Before any framework can work, the team needs a shared starting point. We built Empathy Maps in mixed groups: one engineer, one salesperson, one product manager per group. The disagreements were immediate and productive. “You think the customer sees X? I talked to them last week and they said Y.” Those conflicts surfaced gaps in the collective understanding. Once aligned, we moved to the VPC to channel that shared understanding into product decisions.
The combination play: using frameworks in sequence
The most effective approach I have seen in 10 years of facilitating is not picking one framework. It is knowing the right sequence.
Early exploration: Empathy Map (build understanding) then VPC (structure that understanding into actionable categories)
Competitive analysis: JTBD interviews (understand switching behavior) then VPC (redesign your offer based on what actually triggers decisions)
Product redesign: VPC with real data (map current fit/gaps) then test the assumptions you uncover
New market entry: Empathy Map (capture initial understanding) then JTBD (understand why people in this market switch) then VPC (design your proposition)
The key principle: Empathy Maps generate breadth. JTBD generates depth on switching behavior. The VPC connects customer insight to your value proposition. They work in sequence, not as alternatives.
For the mechanics of filling in the canvas itself, see how to fill in the Value Proposition Canvas.
The mistakes I see when teams pick the wrong framework
After 100+ sessions, certain mistakes repeat.
Using the VPC too early. The team has not talked to customers. They sit around a VPC and fill it in from memory and assumptions. The result looks professional and is entirely wrong. If you do not have customer evidence, use the Empathy Map to map what you think you know, mark the gaps, and go do interviews first.
Using the Empathy Map too long. Some teams love the Empathy Map because it feels productive without being confrontational. You can fill it in without committing to a specific value proposition direction. But at some point you need to move from empathy to action. If your team has done three rounds of Empathy Maps without transitioning to a VPC or a specific product decision, you are hiding behind exploration.
Treating JTBD as a canvas exercise. JTBD is a research methodology, not a worksheet. Teams sometimes try to “fill in the JTBD” like it is a canvas. It does not work that way. JTBD requires structured interviews that trace the customer’s switching timeline. You cannot do it from a conference room.
Mixing frameworks in one session. “Let us do an Empathy Map and a VPC and also discuss Jobs to Be Done, all in a 2-hour workshop.” I have seen this attempted. It creates confusion. Each framework has a different mindset. Pick one per session. You can sequence them across sessions, but do not blend them.
For more on common pitfalls, read about Value Proposition Canvas mistakes that cost teams time and money.
How these frameworks connect to the bigger picture
None of these customer frameworks exist in isolation. They feed into a larger innovation process.
The VPC connects directly to the Business Model Canvas. Your value proposition is one building block of nine. Once you have VPC fit, you still need to validate the rest of the business model: channels, customer relationships, revenue model, cost structure. Teams that perfect their VPC but ignore the business model end up with a great value proposition nobody can deliver profitably. That is the same trap I see with Business Model Canvas vs Lean Canvas comparisons: the tool matters less than whether you are using it to test real assumptions.
The VPC vs Business Model Canvas article goes deeper on how these two tools work together.
Your innovation readiness also determines which framework delivers results. Organizations without direct customer access will struggle with any customer framework. Organizations without cross-functional collaboration will produce siloed insights that never translate to product decisions. Fix the organizational conditions first, or the best framework in the world will not help.
