Map what you build against what customers actually need — then count the connections. Where they don't connect is where your product is wasting effort or missing the point.
▸ Try the interactive toolThe Value Proposition Canvas (VPC), created by Alexander Osterwalder, is a structured tool for checking that a product actually addresses real customer needs. It has two sides, built in a specific order and then connected: the Customer Profile (what the customer experiences) and the Value Map (what the product does).
The two sides are built independently — the profile from research, the value map from your real product — and only then drawn together. Fit is the count of value-map items that connect to a real customer pain, gain, or job. A product with high fit serves genuine needs; one with low fit is busy doing things nobody asked for.
Customer Profile — Jobs (what they're trying to do) · Pains (what frustrates them) · Gains (what they hope for)
Value Map — Products & services · Pain relievers · Gain creators
Most products fail not because they're badly built but because they relieve pains nobody has and create gains nobody wants. The VPC makes that mismatch visible before you've sunk a quarter into it.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Building features in a vacuum | Features get added because they're feasible or fashionable, not because they map to a need. | Every value-map item must connect to a real pain or gain, or it doesn't belong. |
| Assuming you know the customer | Teams build the profile from imagination, not research. | The profile must be built outside-in, from JTBD and interview data — not invented. |
| Confusing activity with value | A long feature list feels like progress. | Fit counts connections, not features — ten unconnected features score zero. |
| No shared language for value | “Why are we building this?” gets a different answer from every function. | The canvas gives one picture everyone reads the same way. |
Start with the customer, not the product. From JTBD and interviews, list their jobs, pains, and gains — and rank each by intensity. This side must come from real data, never assumption.
List what your product actually does today: its services, the pains it relieves, the gains it creates. Be honest — this is the current product, not the aspirational one.
Connect each value-map item to the specific pain or gain it addresses. Count the connections. Unconnected items on either side are the signal.
Two kinds matter: high-intensity pains/gains with no value-map line (unmet needs — opportunities), and value-map items with no customer line (wasted effort — candidates to cut).
Address the highest-ranked unmet pains and gains first. A connection to a trivial gain is worth far less than relieving the customer's most intense pain.
A team listed a dozen polished features in their value map, then built the customer profile from actual interviews. When they drew the lines, half the features connected to nothing — they relieved pains users didn't rank as important.
Meanwhile the customer's single most intense pain had no line to it at all. The team had been adding gain-creators to an already-satisfied area while ignoring the one pain that drove churn.
The deliverable is the two-sided canvas with connection lines drawn — read not as a diagram but as a fit score and a gap list.
| What you see | What it means | Action |
|---|---|---|
| Value-map item with a line | It serves a real, ranked need | Keep — and make sure it serves it well |
| Value-map item with no line | Effort going to something nobody ranked | Question it — candidate to cut |
| High-intensity pain with no line | An unmet need your product ignores | Opportunity — prioritise |
| Low-intensity gain with three lines | Over-serving something that barely matters | Redirect effort to higher-intensity gaps |
Fit is a count, not a feeling. A product can look feature-rich and score near zero on fit — which is exactly how teams ship busy products that don't sell.
The VPC's discipline is building the two sides separately. If you build the profile while looking at your product, you'll unconsciously shape the customer's “needs” to match what you already made. Outside-in first, inside-out second, connect last — the order is the method.
If the jobs, pains, and gains aren't from real research, the whole canvas is fiction with a nice layout. Feed it with JTBD and interviews.
Map what the product does now, not what you wish it did. The gaps are the point; hiding them defeats the exercise.
A long value map is not a high-fit product. Only lines to ranked needs count.
A connection to a trivial gain isn't worth the same as relieving the worst pain. Rank, then prioritise the high-intensity gaps.
JTBD supplies the jobs, pains, and gains for the customer profile. Run JTBD first, then the VPC tests product fit against those jobs.
The vision claims a key benefit; the VPC checks whether that benefit actually connects to a ranked customer need.
The high-intensity unmet gaps become the strongest candidates for the backlog — and the highest-Impact items in RICE.
Both find underserved needs; Opportunity Scoring quantifies at scale what the VPC surfaces qualitatively.
List your product's main features (value map) and, separately, what you genuinely know your users' top pains and gains are (profile). Draw the lines.
Count two things: features with no line, and top pains with no line.
The first number is your wasted effort; the second is your biggest opportunity. Most teams are surprised by how low their real fit count is.