Value Proposition Canvas · Mapping Customer Fit Visually
Alex Osterwalder's two-sided canvas (customer profile + value map) for systematically matching what customers actually want to what your product actually offers. The components, the workflow, and how to use it without making it bureaucratic.
Original concept & attribution. The Value Proposition Canvas was developed by Alex Osterwalder, Yves Pigneur, and the Strategyzer team as a companion to the Business Model Canvas. Their book Value Proposition Design (2014) is the canonical reference. This article reviews the framework and adds operator notes from our use of it.
The two sides
The canvas splits into two halves — Customer Profile (right) and Value Map (left). The goal is to achieve "fit" between them: every customer pain has a corresponding pain reliever, every customer gain has a corresponding gain creator, and every customer job is addressed by a product or service.
Customer profile (the right side)
Customer jobs. The functional, emotional, and social tasks the customer is trying to get done. (See our JTBD guide for depth.)
Pains. Obstacles, frustrations, undesired outcomes, and risks the customer experiences before, during, or after the job.
Gains. Outcomes and benefits the customer wants — required, expected, desired, or unexpected.
Value map (the left side)
Products and services. What you offer.
Pain relievers. How your offering eases specific customer pains.
Gain creators. How your offering produces specific customer gains.
How to use it
The workflow we've found works:
Build the Customer Profile first, and build it from customer research (interviews, support transcripts, sales-call recordings). Don't fill it in from internal opinion — you'll fill it with what you wish customers cared about, not what they actually do.
Rank pains and gains by how often they came up in research and how intensely they were expressed. Not all pains are equal.
Build the Value Map second. For each top-ranked pain and gain, write the specific pain reliever or gain creator your product delivers.
Identify gaps — pains with no reliever, gains with no creator. Those are product opportunities.
Identify wastes — features that don't map to any customer pain or gain. Those are candidates to cut.
RGM operator perspective. The canvas's biggest pitfall is being filled in without research. A canvas full of assumptions is a beautiful artifact of nothing. A canvas built from 10 hours of customer interviews is genuinely useful. The work is the research, not the diagram.
Connecting to other frameworks
The canvas sits between personas (who is this person) and JTBD (what are they trying to accomplish). It's a visual aggregation layer that helps teams see the customer-product mapping at a glance.
It also feeds positioning work. Once you have a clear pain-and-gain map, your positioning statement writes itself: "For [customer with these jobs], who experience [these top pains], our product is [category] that [delivers these specific gain creators], unlike [competitor]."
When to use it (and when not to)
Use it when defining a new product, repositioning an existing one, or onboarding a new product team. Skip it when the team is in execution mode and the customer model is already clear and stable. Filling out canvases for the sake of having artifacts is a common waste.
Related on RGM
Jobs-to-be-Done — the foundational lens for the canvas's "jobs" section.