The value map is the left side of the Value Proposition Canvas. It contains three elements: pain relievers, gain creators, and products and services. Simple enough on paper. In practice, this is where I see the most confusion in my sessions.
After 10 years and 100+ sessions with the Value Proposition Canvas, the pattern is clear. Teams that did solid work on the customer profile sit down to fill in the value map and immediately fall back into feature-listing mode. They write down what their product does instead of what value it creates. The pain relievers section becomes a spec sheet. The gain creators section becomes a copy of the marketing brochure. And products and services? That gets filled in first, when it should be filled in last.
This article breaks down each element of the value map, shows you the difference between doing it right and doing it wrong, and gives you a method to build a value map that actually matches what your customers need.
Book a strategy call about your value proposition
Book your Strategy CallWhat pain relievers actually are
Pain relievers describe how your products and services reduce or eliminate specific customer pains. The key word is “specific.” A pain reliever that says “reduces costs” is not a pain reliever. It is a vague promise.
Every pain reliever in your value map should connect to a specific pain in the customer profile. If you cannot draw a line from a pain reliever to a documented customer pain, it does not belong on the canvas.
Here is the distinction that trips up most teams: a pain reliever is not a feature. A feature is what your product does. A pain reliever is the effect that feature has on a specific customer pain.
Feature vs. pain reliever: examples
| Feature (wrong) | Pain reliever (right) | Customer pain it addresses |
|---|---|---|
| Real-time monitoring dashboard | Eliminates the 4-hour delay between a production fault occurring and the maintenance team finding out | Unplanned downtime costs €8.000 per hour |
| ISO 13485 certified process | Removes 6 weeks from the supplier qualification process | New supplier qualification takes 14 weeks and blocks product launches |
| API integration layer | Eliminates manual data re-entry between production and ERP systems | Staff spends 12 hours per week on duplicate data entry across systems |
| 24/7 support hotline | Ensures production-critical issues get a response within 30 minutes, not next business day | Weekend production failures go unresolved until Monday morning |
See the pattern? The left column describes what you built. The right column describes the effect on a pain the customer actually experiences. Your engineering team writes the left column. Your value proposition needs the right column.
Pain reliever intensity
Not all pain relievers are equal. I use three levels with teams:
Full elimination: the pain disappears completely. “Our automated compliance reporting eliminates the 3-day manual audit preparation your team does every quarter.” These are your strongest value proposition elements.
Significant reduction: the pain gets measurably smaller. “Reduces changeover time from 4 hours to 45 minutes.” Still strong, especially when you can put numbers on it.
Partial relief: the pain becomes more manageable but does not go away. “Provides early warning alerts that give your team 2 hours to prepare for a potential equipment failure instead of reacting after it happens.” Useful, but not enough to build a value proposition around on its own.
When I facilitate sessions with manufacturing companies, I push teams to be honest about which level their pain relievers actually deliver. Calling a partial relief a “full elimination” might feel good in the workshop. It falls apart the moment a customer tests your claim.
What gain creators actually are
Gain creators describe how your products and services produce outcomes and benefits that customers want. If pain relievers are about making bad things go away, gain creators are about making good things happen.
The most common mistake I see: teams list the absence of pain as a gain creator. “Reduces downtime” is a pain reliever. “Enables the plant to qualify for just-in-time delivery contracts with automotive OEMs” is a gain creator. One fixes a problem. The other opens a door.
The gain creator test
Every item in your gain creators section should pass this test: “Does this create a new positive outcome, or does it just remove a negative one?”
Here are examples from B2B and industrial contexts:
| Pain reliever (removes negative) | Gain creator (produces positive) |
|---|---|
| Reduces unplanned downtime by 35% | Frees up €150.000 in emergency maintenance budget for new product development |
| Cuts supplier qualification from 14 weeks to 4 weeks | Enables entry into 3 new material categories per year instead of 1 |
| Eliminates manual compliance reporting | Gives the quality team 15 hours per week to focus on process improvement projects |
| Resolves weekend production failures within 30 minutes | Allows the plant to accept weekend rush orders that competitors cannot fulfil |
The right column is where competitive advantage lives. Any competitor can promise to reduce downtime. Few can articulate how that reduction translates into strategic outcomes for the customer.
Categories of gain creators
Required gains: non-negotiable outcomes. “Must integrate with SAP.” These are table stakes. If you do not deliver them, you are not in the conversation.
Expected gains: outcomes customers assume any decent solution provides. “Should improve efficiency.” Delivering expected gains makes you a commodity.
Desired gains: outcomes customers want but do not expect any vendor to deliver. “The data your system generates could feed our sales quoting process and reduce quote turnaround from 5 days to same-day.” These are the gains that justify premium pricing and create loyal customers.
Unexpected gains: outcomes customers have not thought of. In one session with a packaging manufacturer, we discovered that the production data from a new quality inspection system could be shared with their biggest retail client as proof of batch consistency. That data sharing became a retention tool worth more than the original pain relief. The client did not ask for it. It became the reason they renewed.
Book a strategy call about your value proposition
Book your Strategy CallProducts and services: the HOW, not the WHAT
Products and services is the third element of the value map, and it is the one teams want to fill in first. Resist that urge.
Products and services are the delivery mechanism. They describe what you offer: the software, the service contract, the consulting engagement, the physical product. They are the HOW your pain relievers and gain creators reach the customer.
The correct order for filling in the value map:
- Start with the customer profile (jobs, pains, gains)
- Design pain relievers that address the highest-priority pains
- Design gain creators that produce the most desired gains
- Then list the products and services that deliver those pain relievers and gain creators
Most teams do the opposite. They start with what they have built, list it under products and services, then try to connect it to pains and gains. This is backwards. It creates a solution looking for a problem instead of a solution designed for a specific problem.
I have seen this pattern in at least 60% of the sessions I facilitate. A product team walks in with a detailed feature list and a vague understanding of customer pains. They fill the products and services section in five minutes and spend forty-five minutes struggling to write pain relievers that match. The struggle itself is the signal: if you cannot articulate how your product relieves a specific pain, either you do not understand the pain well enough or your product does not actually address it.
When products and services expose gaps
The value map becomes powerful when it reveals mismatches. You may find:
Pain relievers without products: you identified a real customer pain and know what relief would look like, but you do not have a product that delivers it. That is a product development opportunity.
Products without pain relievers: you built something that does not connect to any documented customer pain. That is a feature looking for a problem. Either find the pain it addresses or question whether it belongs in your value proposition.
Gain creators that require new products: the most valuable gains for customers may require capabilities you have not built yet. That is strategic direction, and exactly the kind of insight the Business Model Canvas helps you act on.
The backward value map problem (and how to fix it)
The single biggest mistake I see with value maps is what I call “backward mapping.” Teams start from their product, list its features, relabel those features as pain relievers, and then try to find customer pains that fit.
This creates a canvas that looks complete but is actually fiction. Every element technically connects, but the connections run in the wrong direction. Instead of “customer has this pain, so we designed this relief,” it becomes “we built this feature, so let us call it a pain reliever and find a pain to attach it to.”
Here is how to tell if your value map is backward:
- Your pain relievers sound like feature descriptions with the word “pain” added
- Every pain in the customer profile conveniently matches something you already offer
- Your gain creators are just the marketing benefits from your product brochure
- You cannot name a single customer pain that your value map does not address (no value map addresses everything)
The fix
Go back to the customer profile. Pick the three highest-priority pains. For each one, answer: “What would need to change in the customer’s world for this pain to be reduced by 50% or more?” Write that answer as a pain reliever, without referencing your product.
Then do the same for the top three gains. “What would need to happen for the customer to achieve this outcome?” Write gain creators in the customer’s language, not yours.
Only after you have pain relievers and gain creators written in customer language do you ask: “Which of our products and services can actually deliver this?” Some will match. Some will not. The ones that do not match are either gaps in your offering or signals that you misidentified the pain.
This is the how to fill in a Value Proposition Canvas approach that produces value propositions worth testing. It forces honesty about what your product actually does for customers versus what you wish it did.
Ranking and prioritizing your value map
A value map with twelve pain relievers and eight gain creators is not a value proposition. It is a list. Customers do not buy lists.
After filling in the value map, I guide teams through a prioritization exercise:
Step 1: Match intensity to priority. Pair each pain reliever with the pain it addresses. Rate the pain’s priority (from the customer profile) and the reliever’s intensity (full elimination, significant reduction, partial relief). Your strongest value proposition elements are high-priority pains with full-elimination relievers.
Step 2: Identify your differentiators. For each pain reliever and gain creator, ask: “Can our top three competitors claim the same thing?” If yes, it is table stakes, not differentiation. Keep it in the value map but do not lead with it.
Step 3: Cut to the core. A focused value proposition has 3-5 pain relievers and 2-4 gain creators. Everything else is supporting detail. This is where teams resist the most. Cutting feels like losing. But a value proposition that tries to say everything says nothing.
The Value Proposition Canvas vs. empathy maps and JTBD comparison shows how different frameworks approach this prioritization. The VPC’s strength is making these trade-offs visible on one canvas.
Once your value map is focused, the next step is validating your value proposition with real customers before committing resources.
The ultimate goal is achieving value proposition fit, where your pain relievers and gain creators match what customers care about most.
Common value map mistakes
I have covered Value Proposition Canvas mistakes broadly, but the value map has its own set of traps that deserve attention:
Listing features instead of pain relievers. The most common mistake. “Cloud-based platform” is not a pain reliever. “Access production data from any location without VPN setup” is. Always translate features into their effect on a specific customer pain.
Confusing pain removal with gain creation. “Reduces downtime” appears in the pain relievers section AND the gain creators section in roughly half the canvases I review. It belongs only in pain relievers. The gain creator is what becomes possible because downtime is reduced.
Ignoring the buying committee. In B2B, different stakeholders experience different pains. The production manager’s pain is “unplanned downtime.” The CFO’s pain is “unpredictable maintenance costs.” The IT director’s pain is “integration complexity.” Your value map needs pain relievers for each stakeholder that matters, not just the end user. This is especially true in manufacturing environments with long procurement cycles.
Making claims you cannot prove. A pain reliever that says “reduces changeover time by 60%” is only valuable if you can back it up with evidence. If you cannot point to a customer case, a pilot result, or a benchmark test, it is a claim, not a pain reliever. This is where testing business ideas becomes part of the value proposition process.
Designing the value map once and never updating it. Customer pains shift. New competitors change what counts as differentiation. Market conditions evolve. Review your value map every quarter at minimum, and every time you get significant new customer evidence.
For a deeper look at how the Value Proposition Canvas works as a complete tool, including the theory behind pain relievers and gain creators, the Strategyzer library is a solid starting reference.
Book a strategy call about your value proposition
In 30 minutes, I’ll diagnose whether your value proposition actually addresses what customers care about most, based on patterns from 100+ canvas sessions. Or book a workshop where your team maps real customer evidence to your value map in one day.
Frequently asked questions
What are pain relievers in the Value Proposition Canvas?
Pain relievers describe how your products and services reduce or eliminate specific customer pains. They are not features. A feature is “real-time monitoring dashboard.” The pain reliever is “eliminates the 4-hour delay between a production fault occurring and your team finding out about it.” Every pain reliever should connect directly to a pain you identified in the customer profile.
What is the difference between pain relievers and gain creators?
Pain relievers reduce or eliminate negative outcomes customers experience. Gain creators produce positive outcomes customers want. Pain relievers answer “how do we make the bad things go away?” Gain creators answer “how do we make the good things happen?” Both connect to the customer profile, but they address different sides of it. A strong value proposition needs both.
How many pain relievers and gain creators should a value map have?
Quality beats quantity. Most effective value propositions focus on 3-5 pain relievers and 2-4 gain creators that directly match the highest-priority pains and gains from the customer profile. A value map with 15 pain relievers is a feature list, not a value proposition. Prioritize the ones where you are measurably better than alternatives.
Where do products and services fit in the value map?
Products and services are the delivery mechanism for your pain relievers and gain creators. They describe what you offer, not the value you create. A product is “predictive maintenance software.” The pain reliever it enables is “reduces unplanned downtime by 35%.” The gain creator it enables is “frees up €150.000 in maintenance budget for innovation projects.” Always fill in pain relievers and gain creators before listing products and services.
Why should you start the value map from the customer profile side?
Starting from the customer profile ensures your value map addresses what customers actually care about. Teams that start from their own products end up listing features and then trying to match them to customer needs. This creates a solution looking for a problem. Start with the customer’s top pains and gains, then design pain relievers and gain creators that address those specific items, then identify which products and services deliver them.
