Value Proposition Canvas (Osterwalder) | Library

The default fill for the problem-discovery slot on L0. The canvas’s customer-profile half is a structured visual map of what the customer is trying to do, what hurts, and what they want.

Despite the name, the canvas does not belong at L2 (Value proposition). Its work is describing the customer’s world, not arguing why a buyer should pick you. Putting it at L2 is the most common misuse in B2B marketing and the source of value propositions that read like feature lists.

What this method does

The canvas has two halves. The Customer Profile (jobs, pains, gains) describes the customer’s world. The Value Map (products, pain relievers, gain creators) describes your product’s response. Only the Customer Profile half is L0 work. The Value Map half is internal feature-to-need alignment, useful for team agreement but not for positioning.

Steps

Focus on the Customer Profile half. Fill it in for one specific audience.

1. List the customer jobs

What is this person actually trying to do, beyond using your product?

Capture all three types of jobs:

Functional jobs. What they are trying to accomplish (finish a report, hire a candidate, ship a feature, close a deal).
Social jobs. How they want to be perceived by their boss, peers, or customers (competent, prepared, in control).
Emotional jobs. How they want to feel during and after the job (confident, calm, in control).

Write each job from the customer’s perspective. Strip out any product or feature words. A job phrased in product terms is a feature wish in disguise.

2. List the pains

What hurts, what risks, what frustrates them about doing the job today?

For each job, name the obstacles. Sort them by type:

Functional pains. Time spent, errors, missed steps, slow processes.
Emotional pains. Anxiety, embarrassment, fear of getting it wrong.
Financial pains. Money lost, time billed for low-leverage work, opportunity cost.
Social pains. Looking bad to a boss, customer, or peer.

A pain in customer language is a job obstacle. A pain in product language is a feature gap, which is solution-thinking dressed up as research.

3. List the gains

What outcomes would make this person’s week or quarter feel like a win?

Gains are not the absence of pain. They are the positive outcomes the customer wants. Capture four kinds:

Required gains. Must-have outcomes for the job to be considered done at all.
Expected gains. What the customer assumes comes with any reasonable solution.
Desired gains. Outcomes they would explicitly ask for if asked.
Unexpected gains. Outcomes that would delight them beyond what they thought to ask for.

The first two protect against churn. The second two create love.

4. Capture severity, frequency, and current workaround

How acute, how often, and what does the customer do about it today?

For every job, pain, and gain, capture three metadata fields:

Severity. High, medium, or low.
Frequency. Daily, weekly, occasional.
Current workaround. What the customer does today instead of using a better solution.

The combination matters more than any single field. A high-severity, high-frequency item with a bad workaround is your strongest opportunity. A low-severity, occasional item with a perfectly fine workaround is not worth solving, no matter how interesting it is.

5. Validate against real customers

Can you quote a real person on each item, or are these still hypotheses?

Until you can quote a real customer on a job, pain, or gain, that item is a hypothesis. Mark hypotheses explicitly. Validate them through interviews before treating them as data.

If your map is built entirely from internal opinion, it is a structured guess. Useful as a starting point. Dangerous as input to downstream layers.

Common pitfalls

Filling the canvas from internal opinion. The map then validates the assumptions that went into it, and the value proposition built on top of it inherits all of those assumptions silently.
Drifting into product language. Jobs, pains, and gains should make sense even if your product did not exist.
Treating the Value Map half as positioning work. It is an internal feature-to-need alignment tool, not an L2 input.
Skipping severity, frequency, and current workaround. Without those, items cannot be ranked, and the canvas becomes a wall of equally-weighted observations.
Filling the canvas for “everyone who might use the product.” Pick one specific audience per canvas. Different audiences have different jobs.

Validation checklist

Before treating the canvas as ready to inform L1 or L2, run it against every item below. If any fail, it is not done.

Each job, pain, and gain is written in the customer’s words, not internal language.
Items are specific to one audience, not to a vague “users of the product.”
Each item carries severity, frequency, and current workaround.
At least half of the items are backed by direct customer quotes. The rest are flagged as hypotheses.
Nothing on the canvas mentions your product or your category.
Someone outside the room could describe the customer’s situation from the canvas alone.

Where the canvas fails

The Value Map half tempts teams into writing a value proposition from the inside out. The output reads like a feature list with feeling-words attached and falls apart in the buyer’s actual decision, which is comparative. For positioning at L2, use Dunford or JTBD, not this.

When to pick a different method at L0

When you need raw qualitative signal rather than structured intake, use interview-based methods (Mom Test, JTBD switch interviews, Steve Blank’s customer development). The canvas is desk research. Interviews are field research. The first organizes what you think you know. The second exposes what you don’t.

Self-check

Can you now use the Value Proposition Canvas?

You should be able to:

Fill in the customer profile half for a specific audience, using real data from interviews or observation rather than internal opinion.
Spot when someone (including yourself) is using the Value Map half as a positioning shortcut.
Recognize when the canvas is the wrong tool because what you actually need is interview-based discovery.
Explain why the canvas belongs at L0 (Problem) and not at L2 (Value proposition).
Apply the severity, frequency, and workaround tags to rank items by genuine opportunity.

If any of these are unclear, re-read the Where the canvas fails section and the Steps it points back to.