This value proposition canvas template maps one customer job, its possible pain and desired gain, and the offer elements meant to address them. Keep an unmatched feature visible instead of inventing a need for it.
Describe one customer job
The original hypothetical case is a conference-speaker slide-review service. Its customer profile starts with three hypotheses:
| Profile area | Working entry |
|---|---|
| Job J1 | Deliver a correctly ordered final slide deck to the event organizer. |
| Pain P1 | Last-minute edits leave several competing file copies. |
| Gain G1 | Know which exact version the organizer will project. |
These are assumptions for the example, not interview findings. The team provisionally chooses version certainty as the need to investigate first.
Strategyzer's Value Proposition Canvas explanation connects customer jobs, pains, and gains with what an offer provides, relieves, and creates. It also calls for testing proposed matches with customer evidence. This scenario and the working tables are original examples.
Put the offer beside the profile
The proposed service contains three elements:
| Offer element | Proposed role | Relationship to P1 and G1 |
|---|---|---|
| O1: Visual slide-polish review. | Review the presentation's visual wording and layout. | May address presentation readability, but the supplied profile has not established that need or a version-control benefit. |
| O2: Explicitly versioned organizer handoff note. | Identify the final deck reference in the handoff. | Hypothesized pain relief for competing copies and gain creation through a specific version reference. |
| O3: Decorative title templates. | Supply title-slide design options. | No match to the supplied pain or gain has been established. |
Select J1, P1, or G1 in the example to inspect the proposed connections. O2 is the strongest match in the team's current hypothesis, because its description addresses the exact version uncertainty. That is a reason to investigate it, not evidence that customers will use or pay for it.
O3 remains unmatched. The team can research whether it serves another important need, change the offer, or leave it out. Filling every feature with an invented pain would conceal the question the canvas is supposed to expose.
Distinguish the product from the value it is supposed to create
For O2, keep the three value-map areas separate:
| Value-map area | Proposed entry |
|---|---|
| Product or service | A versioned organizer handoff note. |
| Pain relief | Reduce uncertainty about which of several copies is intended as final. |
| Gain creation | Give the speaker and organizer an explicit final-version reference to discuss. |
The handoff note is something the service might provide. Its effect on the customer's job is what needs to be tested. The template does not turn a drawn connection into a fit score or a validated-product badge.
Use Compare offers to inspect visual-polish-only wording beside the versioned handoff proposal. Ask what changed in the offer and which assumed need that change addresses.
Choose a research question that could change the map
The proposed conversation begins:
Walk me through the last time you handed a final slide deck to an organizer. Which files and messages did you use, and where did you need to check which version was intended?
Follow the account of the actual handoff, including alternatives the person already uses. The team may discover that version uncertainty matters, that the existing process already handles it, or that another problem deserves attention first.
Leave responses blank until collected. Then connect the actual evidence to the relevant job, pain, gain, or offer assumption. Revise the map where the evidence changes the team's understanding.
Build a map for your own offer
Create one complete, self-contained HTML value proposition working map.
Customer segment and specific job: [DESCRIBE]
Pains and gains, with evidence or explicit hypothesis labels: [PASTE]
Proposed products/service elements: [PASTE]
Pain relief and gain creation expected from each: [PASTE]
Prioritized need and reason for choosing it: [PASTE]
Unsupported matches and open questions: [PASTE]
Next research question and evidence to seek: [PASTE]
Show customer jobs, pains, gains, products/services, pain relievers,
and gain creators. Attribute the method to Strategyzer while making
an original readable layout. Distinguish the offer element from its
hypothesized effect. Label needs and matches by their evidence status.
Let a reader select a job/pain/gain to inspect the offer connections
and rationale. Compare supplied offer variants and retain unmatched
features without inventing a need. Do not generate a fit score or
claim customer demand, adoption, or willingness to pay from assumptions.
Include a blank customer/offer map and temporary research notes.
Identify missing job, offer, or rationale before building a review copy.
Preserve notes across views, mark old output stale after edits, and ask
before resetting. No invented interviews or saved research record.
Use text of at least 16px, labeled keyboard-accessible controls, and
a layout readable at 360px without horizontal scrolling. Put CSS and
JavaScript inline with no external dependencies. Return complete HTML.
Make the uncertain connection easy to review
Before the conversation, ask a teammate to read O2's proposed benefit beside P1. They should be able to identify both the connection and the unanswered question about the customer's current process.
If the map is an HTML page in NOS, edit an overconfident sentence such as “customers need our handoff note” into the hypothesis you will examine. Keep the next interview question beside it. That turns the working copy into a focused research discussion rather than a finished sales claim.