Here’s something I’ve seen happen at least thirty times: a leadership team fills in the Value Proposition Canvas, achieves what looks like perfect fit between their customer profile and their value map, and walks out confident they’ve nailed their value proposition.
Six months later, the product launches. Sales are flat. The team is confused: the canvas showed fit.
The canvas didn’t show anything. The team told the canvas what they wanted to hear.
That’s the core problem with how most teams use the Value Proposition Canvas. The tool is designed to reveal gaps between what customers need and what you offer. But it only works if the customer profile comes from evidence — interviews, support tickets, lost-deal analysis — rather than assumptions. In roughly 60% of the sessions I facilitate, teams start by listing their product features and then reverse-engineer customer needs to match. That’s not customer understanding. That’s a confirmation exercise with sticky notes.
I have run over 100 Value Proposition Canvas sessions in the past 10 years, with manufacturing companies, B2B enterprises, and leadership teams building new offerings with serious money on the line. This guide covers how to use the canvas the way it was designed to be used, the multi-stakeholder B2B reality most guides ignore entirely, and what comes after the canvas is complete. A filled-in canvas with untested assumptions is a hypothesis, not a strategy.
If you’ve watched the explainer video and downloaded the PDF template, this is what comes after.
Book a strategy call about your value proposition
Book your Strategy Call
What is the Value Proposition Canvas?
The Value Proposition Canvas is a strategic tool that maps the relationship between what your customer needs and what you offer. It was developed by Alexander Osterwalder and Yves Pigneur, published in the 2014 book Value Proposition Design, as a companion to the Business Model Canvas.
If the Business Model Canvas shows how your entire business works on one page, the Value Proposition Canvas zooms in on the two most important blocks: Customer Segments and Value Propositions. It takes those two boxes and expands them into a detailed, structured view of why customers should care about what you offer.
The canvas has two sides:
- The Customer Profile (right side): maps what your customer is trying to accomplish, what frustrates them, and what outcomes they want
- The Value Map (left side): maps what you offer, how you relieve their frustrations, and how you create positive outcomes
The goal is fit: the degree to which your value map addresses the jobs, pains, and gains that matter most to your customer.
Here’s what the Value Proposition Canvas is NOT:
- It’s not a messaging exercise. Writing clever taglines is marketing. This is strategy.
- It’s not a feature list. Listing what your product does misses the point entirely.
- It’s not a one-time exercise. If your canvas hasn’t changed since the last time you talked to a customer, it’s stale.
What it IS: a structured way to move from “we think customers want this” to “we have evidence that customers need this, and here’s how we address it.” The canvas forces you to separate what the customer experiences from what you provide, and then see whether those two sides actually connect.
That separation is the entire value of the tool. Teams that skip it end up building solutions for problems nobody has.
The two sides of the Value Proposition Canvas
The Customer Profile
The right side of the canvas, the circle, is about your customer. Not about you. Not about your product. About the human beings (or, in B2B, the people behind the job titles) you’re trying to serve.
It has three components:
Customer Jobs: What your customer is trying to get done. These can be functional (“reduce production downtime below 2%”), social (“be seen as the person who brought innovation to this division”), or emotional (“feel confident that the new equipment won’t fail during peak season”).
Most teams only list functional jobs. That’s a mistake I’ll come back to.
Customer Pains: What annoys, frustrates, or blocks your customer before, during, or after getting a job done. These are risks they fear, obstacles they face, and bad outcomes they want to avoid. “Current supplier takes 6 weeks for spare parts” is a pain. “Board questions every investment without clear ROI data” is a pain. “Afraid of choosing the wrong technology partner and looking incompetent” is a pain.
Customer Gains: The outcomes and benefits your customer wants. Required gains (must-haves), expected gains (the minimum bar), desired gains (they’d love it), and unexpected gains (things they didn’t know were possible). “Reduce total cost of ownership by 15% over five years” is a gain. “Single dashboard showing all production lines” is a gain. “Confidence to present the business case to the CFO without external consultants” is a gain.
The key to the customer profile: specificity. “Wants a better product” is useless. “Needs to reduce changeover time between production runs from 4 hours to under 90 minutes because each hour of downtime costs €12,000”: that’s a customer profile you can build a value proposition around.
The Value Map
The left side of the canvas, the square, is about what you offer. It maps directly against the customer profile:
Products and Services: What you offer. The actual products, services, and combinations of both. Not features, but the full offering as the customer experiences it.
Pain Relievers: How your offering reduces or eliminates customer pains. Not “we have good support.” How, specifically? “24-hour spare parts delivery within the Benelux region” relieves the pain of 6-week waits. “ROI calculator with industry benchmarks included in the proposal” relieves the pain of justifying investments without data.
Gain Creators: How your offering creates customer gains. Again, specific. “Modular design allowing line reconfiguration without new capital expenditure” creates the gain of flexibility. “Quarterly business review with your team to identify next optimization opportunities” creates the gain of ongoing improvement without extra effort.
The fit between them
The whole point of the canvas is to achieve fit: the connection between what customers need and what you deliver. There are three levels:
Problem-Solution Fit: You have evidence that customers have specific jobs, pains, and gains, and you’ve designed a value proposition that addresses them. This is on paper. You believe it works based on research.
Product-Market Fit: You’ve tested your value proposition in the market and have evidence that customers respond positively. They buy, they engage, they come back. The numbers confirm it. (Marc Andreessen defined this well: “being in a good market with a product that can satisfy that market.”)
Business Model Fit: Your value proposition works AND the business model around it is viable. You can deliver the value profitably at scale.
Most teams stop at level one and assume they’ve achieved fit. They haven’t. They’ve achieved a hypothesis. The real work of validation starts after the canvas is complete. I’ll get to that.
How to fill in a Value Proposition Canvas
Start with the customer, not the product
This sounds obvious. It isn’t. In roughly 60% of the sessions I facilitate, the team instinctively starts with the value map, listing their product’s features and then reverse-engineering customer needs to match. That’s backwards. It produces a canvas that confirms your existing assumptions instead of challenging them.
Start on the right. The customer profile. And if possible, start with actual customer data (interview transcripts, support tickets, sales call notes, NPS comments), not with assumptions.
The order that works in practice
After hundreds of sessions, this is the sequence that consistently produces the best results:
1. Choose one customer segment. Not three. Not “enterprise customers.” One specific profile. A procurement manager at a mid-size manufacturer evaluating new production equipment. A head of innovation at a chemical company looking for growth beyond the core business. Get specific or the canvas becomes meaningless.
2. Map customer pains first. Most guides tell you to start with jobs. I don’t. I’ve found that teams have an easier time identifying pains, because the frustrations, obstacles, and risks are concrete and memorable. “Our biggest customer threatened to switch suppliers last quarter because of delivery delays”: that’s a pain everyone in the room understands.
Once you’ve listed pains, ask “why is this a pain?” and you’ll uncover the underlying jobs. Delivery delays are a pain because the customer’s job is keeping production running without unplanned stops. Working backwards from pains to jobs is faster and more accurate than trying to identify abstract jobs from scratch.
3. Map customer gains. What outcomes would make the customer’s life better? Be concrete. “Better service” isn’t a gain. “Same-day response on technical support requests” is.
4. Identify the customer jobs. Now cluster the pains and gains around the underlying jobs. Functional jobs first (what they’re trying to accomplish), then social jobs (how they want to be perceived), then emotional jobs (how they want to feel).
5. Prioritize. This is where most teams skip a step that matters enormously. Not all jobs are equal. Not all pains hurt equally. Not all gains matter equally. Rank them. Which pains keep this person awake? Which gains would make them look like a hero to their boss? Focus on the top three to five of each.
6. Move to the value map. Only now, with a clear, prioritized customer profile, do you map what you offer against it. List your products and services. Then identify specifically which customer pains each element relieves and which gains it creates.
7. Assess fit. Look at the two sides together. Where is there a match? Where are gaps? Are you addressing the most important pains and gains, or just the easy ones?
Solo vs. team
You can draft a canvas alone as a starting point. But the real power comes from a cross-functional team. The product manager sees different customer jobs than the sales director. The service engineer knows pains that marketing has never heard of. The finance lead challenges assumptions about willingness to pay.
I’ve found that four to six people from different functions produces the best canvas. Fewer than four, and you’re missing perspectives. More than six, and the conversation gets unwieldy.
Sticky notes, not typed documents
Same principle as the Business Model Canvas: use sticky notes. One idea per note. Sticky notes communicate impermanence. They say “this is a hypothesis we can move, change, or throw away.” The moment someone types it into a beautifully formatted document, people stop questioning it.
I once had a client who’d hired an agency to create a “final” value proposition canvas. Professionally designed, printed on A1 poster paper, framed. Nobody wanted to challenge it. It looked too finished. We tore it down, put up a blank canvas, and started over with sticky notes. The conversation that followed was completely different from the conversation that had produced the framed version.
Customer jobs, pains, and gains: what most teams get wrong
The customer profile is where the canvas succeeds or fails. Get it right, and the value map almost writes itself. Get it wrong, and you’ll build a convincing-looking canvas on a foundation of sand. For a deep dive into identifying real customer jobs, pains, and gains, see Customer Jobs, Pains, and Gains: how to actually identify them.
The three types of customer jobs
Functional jobs are the tasks your customer is trying to accomplish. “Reduce scrap rate on the production line.” “Evaluate three potential suppliers by the end of Q2.” “Get board approval for a €2M investment.” These are tangible, measurable, and usually what teams list.
Social jobs describe how your customer wants to be perceived by others. “Be seen as someone who makes smart technology decisions.” “Maintain credibility with the engineering team.” “Be known as the person who modernized operations.” These rarely appear on canvases, but they drive behavior more than most teams realize. Clayton Christensen’s Jobs to Be Done work made this point well: customers don’t buy products — they hire them to make progress in specific circumstances.
Emotional jobs describe how your customer wants to feel. “Feel confident the new system won’t fail during the busiest quarter.” “Feel in control of the transition process.” “Not feel anxious when presenting results to the management board.”
Here’s the pattern I see repeatedly: teams list 12 functional jobs, zero social jobs, and zero emotional jobs. Then they wonder why their value proposition, which perfectly addresses the functional requirements, doesn’t move the customer to action.
I worked with an industrial equipment manufacturer that had a technically superior product. Better specs, better reliability data, better total cost of ownership. They lost a major deal to a competitor with objectively worse numbers. When we mapped the customer profile properly, the social and emotional jobs told the story: the purchasing committee had previously approved a supplier that failed, and the person who championed that decision had been reprimanded. The real job wasn’t “find the best equipment.” It was “make a choice that nobody can question afterward.” The competitor won because their proposal included more risk mitigation: phased implementation, guaranteed performance metrics, penalty clauses. They addressed the emotional job. My client addressed the functional one.
After that, we rebuilt the entire value proposition around reducing the customer’s decision risk. Same product. Different value proposition. Very different results.
Where pain identification goes wrong
Listing your own frustrations, not the customer’s. I can’t count how many times I’ve seen “customer doesn’t understand our product” listed as a customer pain. That’s YOUR pain. The customer’s pain might be “took three meetings before I understood what the product actually does for us.”
Being too vague. “High costs” isn’t a pain you can address. “Unplanned maintenance costs averaging €180,000 per year across four production lines” is a pain you can build a value proposition around.
Confusing pains with absence of your solution. “Doesn’t have our software” is not a pain. “Manually reconciles data from three different systems every Monday, taking four hours” is the pain your software might relieve.
Where gain identification goes wrong
Listing features disguised as gains. “Wants a cloud-based platform” is not a gain, it’s a feature preference. The gain is “access production data from any location without VPN issues.”
Ignoring the hierarchy. Not all gains are equal. Required gains are table stakes: miss them and you’re disqualified. Expected gains are the minimum competitive bar. Desired gains are where you differentiate. Unexpected gains are where you create delight and loyalty. Most canvases list everything flat, without distinguishing which level each gain belongs to.
Book a strategy call about your value proposition
Book your Strategy Call
Pain relievers and gain creators: getting the value map right
The value map is where I see the most confusion. Teams consistently make two errors that weaken the entire canvas.
Error #1: Listing features instead of pain relievers
“24/7 customer support” is a feature. The pain reliever is “you’ll never wait more than 15 minutes for a technical response, even at 3AM during a production emergency.” One describes what you have. The other describes what the customer experiences.
For every item on your value map, ask: “How does the customer’s life change because of this?” If you can’t answer that specifically, you’ve listed a feature, not a pain reliever or gain creator.
Error #2: Trying to address every pain and gain
You can’t. No product or service addresses every customer pain and creates every customer gain. And you shouldn’t try. A strong value proposition is focused. It addresses the three to five most important pains and gains brilliantly, rather than all twenty of them poorly.
Osterwalder himself makes this point: the best value propositions focus on a few jobs, pains, and gains and address them extremely well. Trying to cover everything dilutes the message and the product.
I use a simple rule: if your value map has more than eight items on it, you haven’t prioritized. Go back and cut. The items that remain should be the ones where you have genuine, demonstrable strength, not aspirational claims.
The pain reliever / gain creator overlap
Some items relieve a pain and create a gain simultaneously. That’s fine. “Same-day spare parts delivery” relieves the pain of production downtime AND creates the gain of higher uptime percentage. You don’t need to artificially separate them. What matters is that you can trace each item on the value map back to a specific pain or gain on the customer profile.
If an item on your value map doesn’t connect to anything on the customer profile, remove it. It might be a nice feature, but it’s not part of your value proposition for this segment.
When the Value Proposition Canvas works, and when it doesn’t
Like any tool, the canvas has limits. This is the section most guides leave out, probably because the authors are selling VPC workshops or courses.
Where VPC works well
Designing new products or services. When you’re starting from scratch and need structured thinking about who you’re serving and why they’d care, the canvas forces the right conversations early. I use it in every innovation sprint.
Improving existing offerings. When you have an existing product but sales are flat or you’re losing deals you should win, the canvas often reveals why. The customer profile exposes gaps between what you think customers value and what they actually need.
Aligning cross-functional teams. When marketing says one thing, sales promises another, and product builds a third, the canvas creates a single reference point. I’ve used it to get engineering, sales, and marketing aligned in a single session, something that hadn’t happened in years at that company.
Preparing for customer interviews. The canvas is an excellent pre-interview tool. Map what you think the customer profile looks like, then go test it. The canvas gives your interviews structure and focus.
Where VPC falls short
Multi-stakeholder B2B buying decisions. This is the biggest gap, and it affects most of the companies I work with. In industrial B2B, you rarely sell to one person. There’s the end user, the technical evaluator, the procurement officer, the budget holder, and sometimes the board. Each person has different jobs, different pains, different gains. The canvas is designed for a single customer profile. Creating five separate canvases is the standard advice, but five disconnected canvases don’t tell you how to build one coherent value proposition that addresses all five stakeholders. I’ll cover how I handle this below.
Very early exploration. If you genuinely don’t know who your customer is yet, the canvas is premature. You need customer discovery first: go talk to people, observe them, understand their world before you start mapping it in a structured framework. The canvas works best when you have some basis for the customer profile, even if it’s preliminary.
Emotional and status-driven purchases. The canvas structure works well for functional value but struggles with emotional, social, and status-driven value. How do you express “makes the buyer feel like a forward-thinking leader” in a gain box? You can, but it feels forced. For luxury products, premium services, and anything where the emotional value outweighs the functional value, the canvas needs supplementary thinking.
Pricing, distribution, and brand positioning. The canvas tells you what value to create and for whom. It doesn’t tell you what to charge, how to distribute, or how to position the brand. Those are separate strategic decisions. Teams that expect the canvas to answer everything end up disappointed.
What to use instead (or alongside)
| Situation | Better Tool | Why |
|---|---|---|
| Don’t know the customer yet | Customer Discovery Interviews | Need raw data before structured mapping |
| Need to understand emotions and context | Empathy Map | Captures feelings, environment, influences |
| Need deep understanding of motivations | Jobs to Be Done (JTBD) | Goes deeper on “why” behind the job |
| Mapping the full business model | Business Model Canvas | VPC zooms into two blocks of the BMC |
| Testing assumptions | Experiment Design (Testing Business Ideas) | Turns canvas assumptions into testable hypotheses |
For a deeper comparison of these tools, see Value Proposition Canvas vs Empathy Map vs JTBD: A Practitioner’s Decision Guide.
I don’t see this as a competition between tools. I use the VPC, empathy maps, and JTBD interviews in combination, and the choice depends on where the team is in their understanding of the customer. The canvas is one part of the toolkit, not the whole toolkit.
The Value Proposition Canvas in B2B and industrial contexts
This is where I’ve spent most of my career. It’s where the canvas is most useful, and where it’s most often misapplied.
The multi-stakeholder problem
In consumer markets, you usually sell to one person. In industrial B2B, you sell to a buying committee. I worked with a company selling process automation equipment where the buying decision involved:
- The plant manager (cares about uptime and operational simplicity)
- The process engineer (cares about technical specifications and integration)
- The procurement officer (cares about price, contract terms, and supplier risk)
- The finance director (cares about ROI, capex vs opex, and payback period)
- The head of operations (cares about safety, compliance, and training requirements)
Five different profiles. Five sets of jobs, pains, and gains. Some overlapping, some contradictory. The process engineer wants the most technically advanced solution. The procurement officer wants the cheapest.
The standard advice, “create one canvas per persona,” is necessary but not sufficient. You also need:
A priority map. Which stakeholder has the most influence on the decision? In this case, the plant manager had veto power but the finance director controlled the budget. The value proposition needed to win both.
Shared language. A value proposition that speaks engineering to the engineer, finance to the finance director, and operations to the plant manager, without contradicting itself. This requires a core value proposition with stakeholder-specific translations, not five independent messages.
Pain hierarchy across stakeholders. Some pains are universal (everyone hates unexpected costs). Some are stakeholder-specific. The value proposition should address the universal pains prominently and the stakeholder-specific pains in targeted materials.
I handle this by creating individual customer profiles for each stakeholder, then building a single synthesized value map that addresses the two or three highest-priority pains and gains from each profile. It’s more work than the textbook approach. But it produces a value proposition that actually works in a room where five people with different agendas are making a joint decision.
Manufacturing and industrial specifics
Manufacturing companies face constraints that most VPC guides ignore entirely:
Long buying cycles. Equipment purchases can involve 6-18 months of evaluation, site visits, engineering reviews, and regulatory approvals. The customer’s “job” isn’t “buy equipment.” It’s “build a business case that survives 12 months of internal scrutiny.”
Total cost of ownership thinking. Industrial buyers rarely evaluate on price alone. They evaluate on installation cost, operating cost, maintenance cost, energy consumption, spare parts availability, and expected lifespan. Your value map needs to address TCO, not unit price.
Integration with existing systems. No manufacturing customer buys in a vacuum. New equipment must integrate with existing production lines, control systems, ERP software, and quality management processes. “Works with your existing Siemens PLC” is a pain reliever that a consumer product guide would never think to mention.
Regulatory and safety requirements. In many industries, compliance isn’t a nice-to-have, it’s a qualifier. If your product doesn’t meet relevant standards, you’re not in the conversation. This should appear on the customer profile as a required gain, not an afterthought.
For the full guide on applying VPC to manufacturing, see Value Proposition Canvas for Manufacturing.
The mistakes I see over and over
After 10 years and more than a hundred sessions, the patterns are predictable. If you’re about to run a VPC session, watch for these.
Mistake #1: Mixing multiple customer segments on one canvas
The procurement manager and the end user have different jobs, different pains, different gains. When you put them both on the same customer profile, you get a muddled canvas that serves neither well. One segment per canvas. Always.
Mistake #2: Starting with the value map
I’ve already covered this, but it’s worth repeating because it’s the single most common mistake. Teams start by listing their product features, then look for matching customer pains. That’s confirmation bias, not customer understanding. Start with the customer profile. Every time.
Mistake #3: Listing features as pain relievers
“AI-powered analytics” is a feature. “You’ll see production bottlenecks 4 hours before they cause downtime” is a pain reliever. The customer doesn’t care about your technology. They care about what it does for them. Translate every feature into an outcome before putting it on the value map.
Mistake #4: Ignoring social and emotional jobs
In B2B, the assumption is that buying decisions are rational. They’re not. A procurement manager who got burned by a previous supplier has an emotional job: “don’t make a decision I’ll regret.” A head of innovation has a social job: “be recognized as someone who drives real change.” If your canvas only shows functional jobs, you’re missing half the picture.
Mistake #5: Treating the canvas as a one-time exercise
A canvas from January that hasn’t been revisited by March is a museum piece. Customer needs evolve. Competitors move. Markets shift. I recommend revisiting the canvas quarterly at minimum, and immediately after any significant customer feedback, lost deal, or competitive development.
Mistake #6: Never validating the assumptions
This is the big one. A filled-in canvas is a set of hypotheses. “We believe our customers have this pain.” “We believe our product relieves it this way.” Until you’ve tested those beliefs with actual customer evidence (interviews, experiments, market tests) you have an educated guess, not a strategy.
I’ve seen leadership teams spend an entire day building a canvas, leave feeling productive, and never test a single assumption. Six months later, the product launch fails because the core assumption was wrong. The canvas gave them false confidence because they never distinguished between “we believe this” and “we know this.”
For more on common errors, see Value Proposition Canvas Mistakes: 8 Ways Teams Get It Wrong.
Book a strategy call about your value proposition
Book your Strategy Call
From canvas to validation: what happens next
Filling in the canvas is step one. It’s not step ten.
Identify your riskiest assumptions
Every item on your canvas is an assumption until you’ve confirmed it with evidence. Some assumptions are low-risk (“our customers need spare parts,” and you know this because you sell spare parts). Others are high-risk (“our customers would pay a 20% premium for predictive maintenance,” and you’ve never tested this).
After completing a canvas, I ask teams to mark each item with a confidence level:
- Green: We have evidence. Customer interviews, sales data, support records.
- Yellow: We believe this, but the evidence is thin.
- Red: This is a guess.
The red items on the customer profile are where you need to invest in customer research. The red items on the value map are where you need to design experiments.
Test before you build
The methodology for testing value proposition assumptions is well-developed. Osterwalder’s team published Testing Business Ideas with a library of experiments, from discovery interviews to landing page tests to concierge MVPs. For the full practitioner’s guide to running these experiments, see Testing Business Ideas: The Practitioner’s Guide.
The principle is straightforward: spend a little time and money to learn whether your assumptions are true before spending a lot of time and money building on top of them.
For value proposition testing specifically, I recommend starting with:
Customer interviews: Not surveys. Face-to-face conversations where you test whether customers actually experience the pains and desire the gains you’ve mapped. Fifteen interviews with the right profile will tell you more than a thousand survey responses.
Problem-solution fit tests: Show customers the problem you’ve identified (not your solution) and see if they recognize it. If they don’t, your customer profile is wrong.
Value proposition tests: Describe the value you intend to deliver and see if customers respond. Do they lean forward? Do they ask “when can I get this?” Or do they shrug? Their reaction tells you whether you’ve achieved fit or whether you need to iterate.
For the full guide on validation, see How to Validate Your Value Proposition.
The canvas is a living document
Just like the Business Model Canvas, the Value Proposition Canvas should evolve as you learn. After every customer interview, revisit the canvas. After every sales win or loss, revisit the canvas. After every competitive development, revisit the canvas.
The companies that get the most from the VPC treat it as an ongoing practice, not a workshop output that sits in a drawer.
Running a Value Proposition Canvas workshop
If you’re facilitating a session with a team, a few guidelines from experience.
Plan for three hours. Less than two hours and you’re rushing. More than four and you’re overthinking. The sweet spot is 2.5 to 3 hours for one customer segment.
Bring customer data into the room. Print quotes from customer interviews. Bring NPS comments. Show support ticket themes. Real customer voices in the room prevent the session from becoming a guessing game.
Separate divergent and convergent thinking. First 45 minutes: generate ideas freely. Get everything on sticky notes. No filtering, no debate. Then: cluster, prioritize, debate. Mixing the two phases kills both creativity and clarity.
Ban the word “we.” For the first half of the session, while mapping the customer profile, nobody is allowed to talk about the company, the product, or the solution. Customer profile time is about the customer. I’ve literally stopped people mid-sentence when they start with “but we could…” Not yet. Customer first.
End with three questions, not a finished canvas. The best outcome isn’t a completed poster. It’s a shared understanding of the customer plus a clear list of “what don’t we know?” Those unknowns become your testing agenda.
In 30 minutes, I will diagnose what is actually blocking your value proposition design, based on patterns from 100+ canvas sessions. Or book a hands-on workshop where your team maps, challenges, and redesigns your value proposition in one day.Book a strategy call about your value proposition
Frequently asked questions
What is the Value Proposition Canvas?
The Value Proposition Canvas is a strategic tool developed by Alexander Osterwalder and Yves Pigneur that maps the relationship between what customers need and what you offer. It has two sides: the Customer Profile (jobs, pains, and gains) and the Value Map (products/services, pain relievers, and gain creators). The goal is achieving fit — ensuring your offering addresses the most important customer needs. It was published in the 2014 book Value Proposition Design and works as a detailed companion to the Business Model Canvas.
What are the 6 elements of the Value Proposition Canvas?
The canvas has six elements across two sides. The Customer Profile contains: (1) Customer Jobs — what the customer is trying to accomplish, (2) Customer Pains — frustrations, obstacles, and risks, and (3) Customer Gains — desired outcomes and benefits. The Value Map contains: (4) Products and Services — what you offer, (5) Pain Relievers — how you reduce customer pains, and (6) Gain Creators — how you create customer gains. The two sides should connect: each pain reliever should address a specific pain, and each gain creator should address a specific gain.
How do you fill in a Value Proposition Canvas?
Start with the Customer Profile, not the Value Map. Choose one specific customer segment. Map their pains first (concrete frustrations are easiest to identify), then gains, then cluster them around underlying jobs. Prioritize — focus on the top three to five of each. Only then move to the Value Map: list your offerings and identify specifically how each one relieves a pain or creates a gain. Assess fit by checking whether your value map addresses the most important items on the customer profile. Use sticky notes, work with a cross-functional team, and treat every item as a hypothesis to test. For the full process, see How to Fill In a Value Proposition Canvas.
What is the difference between a Value Proposition Canvas and a Business Model Canvas?
The Business Model Canvas maps nine building blocks of how an entire business works — from customers to costs. The Value Proposition Canvas zooms in on just two of those blocks: Customer Segments and Value Propositions. Think of it as a magnifying glass. The BMC tells you what your business model looks like; the VPC tells you why customers should care about it. I use both in most engagements: BMC for the big picture, VPC for the depth on customer-value fit. For more detail, see Value Proposition Canvas vs Business Model Canvas.
What are customer jobs, pains, and gains?
Customer jobs are what your customer is trying to accomplish — functional tasks (reduce production downtime), social objectives (be seen as a competent decision-maker), or emotional goals (feel confident about a major purchase). Pains are the frustrations, obstacles, and risks they experience when trying to get those jobs done. Gains are the positive outcomes they want to achieve. The key is specificity: “wants a good product” is useless; “needs changeover time under 90 minutes because each hour of downtime costs €12,000” gives you something to work with. For more, see Customer Jobs, Pains, and Gains: How to Actually Identify Them.
When should you use a Value Proposition Canvas?
Use it when you need to understand why customers should care about what you offer — whether you’re designing a new product, improving an existing one, entering a new market, or trying to understand why you’re losing deals. It works best when you have some basis for the customer profile (even preliminary research) and want structured thinking about customer-value fit. It’s less useful in very early exploration (when you don’t know your customer yet — do customer discovery first) or for decisions about pricing, distribution, and brand positioning (those require different tools).
How many Value Proposition Canvases do you need?
One per customer segment. If you sell to procurement managers and plant operators, those are two different profiles with different jobs, pains, and gains — you need two canvases. In B2B, where buying decisions involve multiple stakeholders, you may need three to five canvases plus a synthesized view. The common mistake is cramming multiple profiles onto one canvas, which produces a muddled result that serves nobody well.
Can you use the Value Proposition Canvas for existing products?
Absolutely — and I’d argue that’s where it’s often most valuable. Mapping an existing product against a current customer profile reveals gaps between what you think your value proposition is and what customers actually experience. I’ve used the canvas with established companies that discovered their stated value proposition — the one on their website — had almost no connection to why customers actually bought from them. That disconnect is gold once you see it.
What to do next
If you’ve read this far, you’re serious about using the Value Proposition Canvas as a strategic tool, not just filling in boxes.
Here’s what I’d recommend:
- Pick your most important customer segment. Not the easiest. The one where getting the value proposition right would have the biggest impact.
- Map their pains first. Talk to your sales team, your service team, your account managers. What frustrates this customer? What makes them hesitate? What complaints keep coming up?
- Build the customer profile before touching the value map. Resist the urge to jump to solutions.
- Mark your confidence level. Green, yellow, red. Be honest about what you know versus what you assume.
- Test the reds. Design simple experiments or interviews to validate your riskiest assumptions before investing in development or campaigns.
Value proposition design requires the organizational conditions for it to actually produce change. If your organization punishes experimentation or doesn’t protect resources for new ideas, the best value proposition work in the world won’t move the needle. The Innovation Readiness Assessment identifies the nine conditions that determine whether this kind of work sticks.
And if you’d like to work through this with someone who has done it hundreds of times across industrial B2B companies, let’s talk.
