Value propositions

How to fill in a Value Proposition Canvas: the questions most guides skip

Most guides tell you to start with customer jobs. That is not how it works in practice. After 100+ sessions, I start with pains, not jobs. Here is the step-by-step order that actually produces useful canvases, plus the questions most teams forget to ask.

Ton van der Linden·How-to·Last updated 28 March 2026·13 min read
How to fill in a Value Proposition Canvas: the questions most guides skip

You have a blank Value Proposition Canvas in front of you. Maybe printed on A1 paper. Maybe on a screen. The team is assembled. Someone says, “Let’s start with customer jobs.”

That is where most sessions go wrong.

Not because customer jobs are unimportant. But because starting with jobs produces abstract, corporate-sounding answers that nobody in the room can verify. “Our customer wants to grow revenue.” Of course they do. That tells you nothing about how to fill in a Value Proposition Canvas that actually leads to better decisions.

After 100+ sessions with the Value Proposition Canvas over the past 10 years, I have settled on a different order. One that consistently produces better canvases, more honest conversations, and fewer wasted sticky notes. This article walks through that order step by step, including the questions I ask that most guides leave out, and what to do when your team cannot agree on what belongs on the canvas.

If you want the full background on the tool itself, start with the practitioner’s guide to the Value Proposition Canvas. This article assumes you know what the canvas is. It is about how to fill it in properly.

Request a Strategy Call about your value proposition

In 30 minutes, I'll pinpoint where your value proposition connects with what customers need, and where it doesn't. Or book a workshop where your team builds customer profiles from evidence, not assumptions.

Before you touch the canvas: two things to get right

Pick one customer segment

One. Not “SMBs and enterprise.” Not “procurement and engineering.” One specific person with a specific role in a specific context.

A procurement manager at a mid-size manufacturer evaluating new production equipment. A head of innovation at a chemical company looking for growth beyond the core business. A plant manager responsible for reducing downtime on three production lines.

If you try to capture multiple segments on one canvas, you will get a muddled profile that serves none of them well. This is one of the most common Value Proposition Canvas mistakes I see.

In B2B, you will eventually need multiple canvases for the different stakeholders in a buying decision. I cover that further down. But start with one.

Gather your evidence first

Here is a question I ask before every session: “What customer evidence do we have?”

I mean actual evidence. Interview transcripts. Support tickets. Lost-deal analyses. Win reports. NPS comments with the specific text, not just the score. Emails where a customer explained why they chose a competitor.

If the answer is “nothing,” the session can still be useful, but everyone needs to understand that the canvas they produce is a set of guesses, not a strategy. A canvas built on assumptions needs to be tested before anyone builds on it. I will come back to this.

The best sessions I have facilitated started with the team reading five customer interview transcripts out loud. Twenty minutes of reading before a single sticky note goes on the wall. It changes everything about the quality of what follows.

Step 1: start with pains, not jobs

This is where I break from the textbook. Most guides, including Alexander Osterwalder’s Value Proposition Design, suggest starting with customer jobs. I start with pains.

Why? Because pains are concrete. They happened. People remember them.

Ask a team “What are your customer’s jobs?” and you get polished, abstract answers. Ask “What frustrates your customer? What went wrong in the last deal? What complaints does the support team hear every week?” and suddenly the room gets specific.

“The customer called three times about delivery delays in Q3.” That is a pain everyone can picture. And it leads to better jobs than “wants reliable delivery” ever would.

The questions to ask about pains

Most teams list pains too quickly. They write three sticky notes and move on. These questions slow the conversation down and surface the pains that matter:

  • What did the customer complain about in the last six months?
  • What made them almost cancel, or actually cancel?
  • What part of working with us (or our competitors) takes too long?
  • What information do they lack when they need to make a decision?
  • What risks worry them that they might not say out loud?
  • What do they have to explain to their boss that they wish they did not have to?

That last question is gold in B2B. It surfaces internal pains that have nothing to do with your product but everything to do with the buying decision.

The trap: listing your pains, not theirs

I see this in almost every session. Someone writes “customer does not understand our product” as a customer pain.

No. That is your pain. The customer’s pain might be: “took three meetings before I understood what this product actually does for us.” Or: “cannot explain the technical difference to the board without sounding like I do not know what I am talking about.” The pain lives in the customer’s world, not yours.

Step 2: map the gains

With pains on the wall, move to gains. What outcomes would make the customer’s situation better?

A useful distinction here: gains are not the opposite of pains. “No delivery delays” is the absence of a pain. “Receive a notification 48 hours before shipment with exact delivery window” is a gain. One removes a negative. The other creates a positive.

The questions to ask about gains

  • What would make them look good to their boss?
  • What would make the next buying decision easier for them?
  • If they could wave a magic wand about this part of their business, what would change?
  • What do they measure and report on?
  • What would they brag about at an industry conference?

The trap: confusing features with gains

“Wants a cloud-based platform” is not a gain. It is a feature preference. The gain behind it: “access production data from any location without VPN issues.” Always ask: what does the customer get from this? What changes in their daily work?

For the full breakdown of how to identify customer jobs, pains, and gains properly, see the deep-dive on customer jobs, pains, and gains.

Step 3: cluster pains and gains into jobs

Now you have a wall full of specific pains and specific gains. Step back and ask: what is the customer actually trying to get done?

The pains and gains will cluster around underlying jobs. Delivery complaints, inventory frustrations, and production downtime all cluster around the job “keep my production line running without unplanned stops.” Complaints about justifying purchases, missing ROI data, and board pushback cluster around “build a business case that survives internal scrutiny.”

Three types of jobs (and why most teams miss two of them)

Functional jobs are what the customer is trying to accomplish. “Reduce changeover time between production runs.” “Evaluate and select a new automation partner.”

Social jobs describe how the customer wants to be perceived. “Be recognized as the person who modernized our production.” “Not be seen as the one who chose the wrong supplier.”

Emotional jobs describe how the customer wants to feel. “Feel confident presenting this investment to the board.” “Not feel anxious about whether this equipment will perform during peak season.”

I see the same pattern in almost every session: teams list twelve functional jobs, zero social jobs, and zero emotional jobs. Then they build a value proposition that addresses all the functional requirements perfectly and still loses the deal. Because the customer’s real decision was driven by “I cannot afford to pick the wrong supplier again.”

The trap: too many jobs

If you have more than eight jobs on the canvas, you have not prioritized. Go back and rank them. Which three jobs matter most? Which pains keep this person up at night? Which gains would make them a hero inside their organization?

The canvas only becomes useful when you force yourself to choose.

Step 4: move to the value map

Only now, with a prioritized customer profile, do you touch the left side of the canvas.

Products and services

List what you offer. Not features. The offering as the customer experiences it. “Predictive maintenance service with quarterly on-site inspection” is an offering. “AI-powered analytics” is a feature that means nothing to the customer without context.

Pain relievers

For each of the top pains on the customer profile, ask: how does our offering reduce or eliminate this pain?

Be specific. “Good customer support” is not a pain reliever. “24-hour spare parts delivery within the Benelux” relieves the pain of production stops caused by long spare-part lead times.

The question that separates a useful pain reliever from a vague one: Can the customer tell the difference before and after? If they cannot, it is not specific enough.

For a full treatment of pain relievers and gain creators, see Pain relievers and gain creators: how to get the value map right.

Gain creators

For each of the top gains on the customer profile, ask: how does our offering create this outcome?

“Modular equipment design that allows line reconfiguration without new capital expenditure” creates the gain of production flexibility. “Quarterly business review with benchmarking data from your industry” creates the gain of continuous improvement without extra internal effort.

The trap: trying to address everything

You cannot relieve every pain and create every gain. A strong value proposition focuses on the three to five most important pains and gains and addresses them extremely well. Trying to cover everything dilutes both the canvas and your actual value proposition.

I use a simple rule: if your value map has more than eight items, you have not prioritized. Cut until what remains represents genuine, demonstrable strength.

Step 5: assess fit and mark your assumptions

Put both sides next to each other. This is the moment of truth.

Three questions to assess fit

  1. Are you addressing the most important pains and gains, or just the easy ones? Teams consistently address the pains they can solve rather than the pains that matter most to the customer. If the customer’s number-one pain is “I cannot get board approval for this kind of investment” and none of your pain relievers touch that, your value proposition has a gap where it counts.

  2. Are there items on the value map that do not connect to anything on the customer profile? Remove them. They might be great features, but they are not part of your value proposition for this segment.

  3. Where are the gaps? Important pains with no pain reliever. High-priority gains with no gain creator. These are either opportunities to improve your offering or signals that this customer segment is not the right fit for what you have today.

Mark every item: evidence or assumption?

This is the step that transforms the canvas from a planning exercise into a tool for action. Go through every sticky note and ask: do we know this, or do we believe this?

MarkerMeaningNext step
GreenWe have evidence: interviews, data, sales recordsKeep, but revalidate quarterly
YellowWe believe this based on experience, but evidence is thinDesign a quick test
RedThis is a guessTest before building anything on it

A canvas full of green notes is a strategy. A canvas full of red notes is a hypothesis. Both are useful, but they require very different next steps.

The red items on the customer profile need customer research. The red items on the value map need experiments. For the full process of turning canvas assumptions into experiments, see How to test business assumptions. For the broader methodology, see Testing Business Ideas.

When the team disagrees (and why that is a good sign)

In roughly half the sessions I facilitate, the team disagrees. The sales director says the biggest customer pain is price. The product manager says it is functionality. The service engineer says it is response time.

Most facilitators try to resolve this in the room. I do not. Disagreement means you have different assumptions about the customer. That is valuable information.

Here is what I do instead:

  1. Write each version on a separate sticky note
  2. Mark all of them as red (assumption)
  3. Ask: “How would we find out which one is true?”
  4. Design a test. Usually five customer interviews focused on that specific question

Never resolve a disagreement about customer needs by voting. Never let the highest-paid person in the room win by default. Resolve it with evidence.

I worked with a manufacturing company where the sales team was convinced that price was the only thing customers cared about. The product team believed customers valued technical specifications above all else. We ran ten interviews. The actual top pain? Integration complexity. Neither team had it on their list. Both had been building their arguments on assumptions they had never tested.

The B2B multi-stakeholder reality

In industrial B2B, you rarely sell to one person. A typical buying decision involves three to seven stakeholders. Each has different jobs, different pains, different gains. Sometimes contradictory ones. The process engineer wants the most advanced technical solution. The procurement officer wants the lowest price. The plant manager wants the least disruption to current operations.

How I handle it

  1. Create one canvas per stakeholder type. Not one mega-canvas. The procurement manager gets a separate canvas from the plant manager.

  2. Build a priority map. Which stakeholder has the most influence on the final decision? Who has veto power? In many industrial companies, the finance director controls the budget while the plant manager has veto power on technical fit.

  3. Find the overlapping pains. Some pains are universal: everyone hates unexpected costs, everyone wants less risk. These are the foundation of your value proposition.

  4. Address stakeholder-specific pains in targeted materials. The core value proposition addresses shared pains. Stakeholder-specific pains get addressed in the right conversations and documents.

For the complete guide to multi-stakeholder canvases, see Value Proposition Canvas for B2B.

For manufacturing-specific examples and constraints, see Value Proposition Canvas for Manufacturing.

Quick reference: the fill-in sequence

StepWhat to doKey questionCommon trap
0Pick one segment, gather evidenceWhat customer data do we have?Skipping evidence gathering
1Map customer painsWhat frustrated them recently?Listing your pains, not theirs
2Map customer gainsWhat would make them look good?Confusing features with gains
3Cluster into jobs (functional, social, emotional)What is the customer trying to get done?Only listing functional jobs
4Prioritize the customer profileWhich 3-5 matter most?Keeping everything on the canvas
5Map products, pain relievers, gain creatorsHow does our offering change their situation?Listing features, not outcomes
6Assess fitAre we addressing the most important items?Addressing easy pains, not important ones
7Mark evidence vs. assumptionsDo we know this, or believe this?Treating all items as facts

What happens after the canvas is done

A filled-in canvas is not a finished strategy. It is a set of hypotheses organized on one page.

The next steps depend on what color your sticky notes are. If most are green, you have a solid foundation to build your value proposition, marketing, and sales approach. If most are red, you need to test before you invest.

Testing does not mean months of research. Five well-structured customer interviews can resolve most assumption gaps. A simple landing page test can tell you whether customers respond to the value proposition you have designed. The methodology is well-developed, and I use it in every engagement. For the full approach, see Testing Business Ideas.

The canvas also connects to the bigger picture. Your value proposition is two blocks of the Business Model Canvas. Every value proposition lives inside a business model. For how to fill in the broader Business Model Canvas, see How to fill in a Business Model Canvas. And if you are working on multiple value propositions for different segments or markets, those need to be managed as a portfolio. That is where Innovation Portfolio Management comes in.

For real-world examples of completed canvases across different industries, see Value Proposition Canvas Examples.

For how to take your canvas from hypothesis to validated value proposition, see How to Validate Your Value Proposition.

Before starting any of this, consider whether your organization is set up to act on what you discover. The best canvas in the world does not help if your company lacks the structure to turn insights into action. The Innovation Readiness Assessment helps you understand where you stand.

Frequently asked questions

What is the best order to fill in a Value Proposition Canvas?

Start with the customer profile (right side), not the value map. Within the customer profile, start with pains first because they are concrete and get teams talking honestly. Then map gains. Then cluster pains and gains into customer jobs. Only move to the value map after you have a prioritized customer profile. This order produces better results than the textbook sequence of jobs-pains-gains.

Should I fill in the Value Proposition Canvas before or after talking to customers?

Both. Fill in a first draft based on what you currently know, then mark every item as evidence-based or assumption. Use that draft to structure your customer interviews. After the interviews, rebuild the canvas with real data. The first version is a hypothesis. The post-interview version is where the real value starts. For the methodology on testing your canvas assumptions, see Testing Business Ideas.

How many Value Proposition Canvases do I need for B2B?

One per stakeholder type involved in the buying decision. In industrial B2B, a typical purchase involves three to seven stakeholders with different jobs, pains, and gains. Create separate canvases for each stakeholder type, then build a priority map to identify which pains and gains overlap across stakeholders. For manufacturing-specific guidance, see Value Proposition Canvas for Manufacturing.

What do I do when my team disagrees on the customer profile?

Disagreement is valuable. It means you have different assumptions in the room. Write each version on a separate sticky note and mark it as an open question. Then design a simple test to resolve it, usually five customer interviews focused on that specific point. Never resolve disagreements about customer needs by voting or seniority. Resolve them with evidence.

How often should I update the Value Proposition Canvas?

At minimum quarterly. Immediately after any lost deal, major customer complaint, or competitive shift. A canvas that has not changed in six months is probably based on outdated assumptions. Treat it as a living document that evolves with every new piece of customer evidence. For more on keeping your canvas current and avoiding common decay patterns, see Value Proposition Canvas mistakes teams keep making.

Innovation Insights

Get Innovation Insights in your inbox

One email a month: the newest guides and practitioner notes, from business model design to innovation readiness, plus dates for upcoming masterclasses. Written from what actually happened in the room, at 50+ companies. No daily drip, no sales sequence.