Value Proposition Canvas

What it is

A framework co-created by Alexander Osterwalder that maps a product's value proposition against a specific customer segment's needs, pains, and gains. The canvas consists of two halves: the customer profile (what jobs, pains, and gains matter to them) and the value map (what features, pain relievers, and gain creators your product offers). Positioning emerges from the fit between what you offer and what the segment needs. Where Jobs-to-be-Done focuses on identifying the single job a customer is trying to accomplish, the Value Proposition Canvas goes a layer further: it maps every pain and gain attached to that job and checks, item by item, whether the product actually addresses each one, which makes it as useful an audit tool as it is a positioning tool.

When to use it

• During product development, to ensure your roadmap aligns with customer jobs and pain points
• When defining positioning for different customer segments (B2B vs. B2C, enterprise vs. SMB, etc.)
• To identify messaging angles you haven't explored: gaps between what you offer and what customers care about
• When repositioning or launching to a new segment
• As a shared tool for cross-functional alignment on customer value (product, marketing, sales, support)
• Before a roadmap prioritisation exercise, to check whether planned features actually map to a documented pain or gain rather than an internal assumption
• When win/loss data shows deals lost to "good enough" incumbents, a signal the value map may be over-indexed on features customers don't rate as pains or gains

Ownership

At a scaled company, a Head of Product Marketing owns the completed canvas, typically co-building the customer profile half with a Product Manager or UX researcher and retaining sole ownership of the value map and fit analysis. A solo or founding PMM builds both halves alone, drawing on their own customer conversations rather than a separate research function. Where the fit analysis feeds roadmap prioritisation, Product Management should review it jointly with PMM before it changes roadmap priority, since each function carries evidence the other lacks.

How to apply it

1. Profile Your Customer:

   • Jobs: What does this segment try to accomplish? (functional, emotional, social jobs). Source these from interviews and support transcripts rather than internal assumptions; teams that write the customer profile from their own mental model of the customer consistently overestimate how much customers care about the product category itself, as opposed to the job behind it.
   • Pains: What obstacles, frustrations, or risks prevent them from achieving their jobs? Separate pains by severity: a mild annoyance and a business-critical risk both count as "pains" but deserve very different weight.
   • Gains: What outcomes or benefits would make the job easier or more valuable? Include both required gains (table stakes the customer expects) and unexpected gains (delighters that exceed expectation); the two need different messaging treatment.

2. Map Your Value Proposition:

   • Features/Products: What do you build or offer? List these plainly, without adjectives, so the mapping in the next step stays honest.
   • Pain Relievers: Which of your features directly address customer pains? For each, write the mechanism, not just the claim: "automated invoice reminders" is a feature; "removes the two hours per week finance spends chasing late payments" is a pain reliever.
   • Gain Creators: Which of your features create outcomes customers want? Apply the same mechanism discipline as pain relievers.

3. Analyse the Fit:

   • Does each major customer pain have a corresponding pain reliever? If not, you have a gap.
   • Does each customer gain have a corresponding gain creator? If not, you're under-delivering.
   • Are there features you offer that don't address any customer pain or gain? These are noise; deprioritise them, or at minimum keep them out of primary messaging even if they stay in the product.
   • Score the fit for each pain and gain (strong, partial, none) so gaps are visible at a glance, and revisit the lowest-scoring items first in the next roadmap cycle.

4. Refine Messaging: Prioritise messaging around pain relievers and gain creators that matter most to the segment. Avoid talking about features that don't map to customer needs, even if they were expensive to build; internal pride in a feature is not a reason to lead with it externally.

5. Iterate: As you learn more about customer needs, update the canvas. Share updates with product and sales to keep teams aligned. Treat the canvas as a living document tied to a cadence (quarterly is typical), not a one-off workshop output that gets filed away after the initial positioning exercise.

6. Validate the fit with customers directly: Show the completed canvas, or the resulting messaging drawn from it, to five to eight target customers and ask them to point out anything that feels exaggerated or anything important that's missing. This catches internal blind spots before they reach a website or sales deck.