Use the Value Proposition Canvas for one customer segment and one offer at a time. Map the customer’s jobs, pains and gains separately from your products, pain relievers and gain creators. Rank what matters, connect only the strongest matches and label every item as evidence or assumption. The canvas is a thinking and testing tool; completing every box does not prove customer value.
Understand the two sides
Strategyzer’s official canvas separates:
- Customer profile: jobs the customer is trying to complete, pains that obstruct them and gains they seek.
- Value map: products and services, pain relievers and gain creators.
The separation matters. It prevents a feature from being rewritten as a customer need without evidence. Read the broader value proposition guide if the final customer-facing statement is your immediate task.
Prepare before the workshop
Choose a specific segment and situation. Collect evidence from interviews, observations, sales conversations, support requests and product behaviour. Give each note a source and date.
Create three evidence labels:
- Observed: directly seen or heard in relevant research.
- Supported: repeated across credible sources or behaviour.
- Assumed: plausible but not yet checked.
The GOV.UK Service Manual recommends treating views that do not come from users as assumptions to be researched. That discipline makes the canvas more honest.
Fill the customer profile first
Jobs
Describe what the customer is trying to accomplish—not what they do with your product. Include practical, social and emotional dimensions only when evidence supports them.
Pains
Record obstacles, risks and undesirable outcomes. Make them contextual: “waiting two days for finance approval during supplier onboarding” is more useful than “inefficiency”.
Gains
Describe outcomes the customer values. Separate required gains from pleasant extras.
Rank all three. A canvas with 30 equal sticky notes offers no direction.
Build and connect the value map
List the product or service, then state exactly how each important capability relieves a ranked pain or creates a ranked gain. Draw connections only where the logic is credible.
Use this fit check:
| Customer evidence | Offer response | Proof needed |
|---|---|---|
| Important job | Enabling capability | Demonstration or usage evidence |
| Costly pain | Pain reliever | Customer or operational evidence |
| Desired gain | Gain creator | Outcome evidence |
Then decide what to test using How to Test a Value Proposition.
Illustrative example
Illustrative example: consider freelance accountants collecting records from microbusiness clients.
- Job: obtain complete records before beginning year-end accounts.
- Pain: documents arrive across channels and missing items are difficult to track.
- Gain: know which client is ready without checking every conversation.
- Offer: a guided document-request portal.
- Pain reliever: one visible list of received and missing items.
- Gain creator: readiness status across all clients.
- Proof needed: a workflow demonstration and evidence from relevant practices.
This hypothetical map should not assume that “readiness status” matters most. Interviews might reveal that client adoption or deadline risk is more important.
Common canvas mistakes
- Combining several segments whose priorities differ.
- Writing features on the customer side.
- Treating brainstorming volume as evidence.
- Connecting every capability to every need.
- Ignoring current alternatives and buying constraints.
- Stopping when the workshop ends.
When evidence is thin, use Writing a Value Proposition Without Customer Proof to keep claims proportionate.
Limitations and trade-offs
The canvas is a simplified representation. It does not cover market size, competition, pricing, delivery economics or every buying role. It can make a team feel aligned because everyone sees the same page, even when the content is speculative.
Use it alongside market analysis and direct research. Maintain versions so later changes reflect new evidence rather than workshop memory.
Frequently asked questions
How many canvases should we create?
Create one for each materially different customer segment and offer. Merge them only when the jobs, priorities and value logic genuinely overlap.
Should customers fill in the canvas?
Usually the team synthesises evidence into it. Customers provide experiences and decisions, not responsibility for your strategy.
When is the canvas finished?
Never permanently. Treat it as current when the priority items are supported well enough for the decision at hand, then update it after material learning.
Your useful next step
Print or open one blank canvas. Add only notes linked to a source, mark assumptions in a different colour and circle the three most important matches. Create a test for the riskiest circled assumption.
