Build the Fit Before You Build Anything Else

A product doesn’t usually fail because the build was bad. It fails because nobody has proved on paper that a customer actually wanted it in the first place.

The Value Proposition Canvas, developed by Alexander Osterwalder as a detailed extension of his Business Model Canvas, exists to force that proof. It has two halves. On one side, a customer profile: the jobs your customer is trying to get done, the pain points they hit doing them, and the gains they're actually after. On the other, a value map: the products and services you offer, the pain relievers, and the gain creators. The discipline sits in the order you fill them. You build the customer profile first, independently of your product, then check whether your value map genuinely addresses what you found.

Get the order backwards, and you end up designing your ideal customer to match the product you already wanted to build, rather than the other way round. It's easy to treat that discipline as optional: a poster from a workshop, filled in once, argued over in a room full of opinions, then quietly forgotten the moment delivery starts. The canvas isn’t the value. The value comes through comparing two independently built halves and building only once they demonstrably fit.

Nissan and Tesla make the point better than any abstract explanation.

Nissan's Leaf ticks plenty of boxes on paper: advanced tech features, multiple industry awards, real savings from tax credits. But set that value map against the customer profile of someone wanting personal mobility, long trips, and a desire to stand apart from the crowd, and it falls apart. A frequently seen, best-selling car contradicts the idea of "be different." Slow charging and a thin charging network aren't relieved by savings or sales figures. The verdict is a misfit, despite genuinely good engineering.

On the other hand, Tesla's value map, tested against the same customer profile, matches almost line for line: a growing charging network addresses charging pain directly; an eight-year battery warranty addresses durability; a reputable and distinctive brand addresses the desire to stand apart. Same customer, same market, two very different outcomes, because one team proved the fit and the other assumed it.

That's the lesson worth sitting with: teams rarely fail because they lack a good product. They fail because they never proved, in writing, which pains and gains that product was actually solving for.

This is precisely what Design at Scale™ asks for under Proposition Shaping, and it isn't a new requirement layered on top of what you already do. Our Customer Research tool asks the same three questions the canvas forces: is the proposition based on business or user needs, is that documented anywhere, and does it define a target market? Design Shaping carries the value-map side of the same exercise forward, requiring defined personas and target audiences, and validation of the landscape "via Prototypes” rather than assumption.
You don't need Osterwalder’s specific circle-and-square template to satisfy this. You need some version of the fit-check to exist, and to be written into the Proposition Identification Document alongside High-Level Requirements and Acceptance Criteria. Hence, the pains and gains you’re solving for are visible to business, design, and engineering alike, not just remembered by whoever ran the workshop.

Three common responses:

"We don't have time for a formal canvas workshop"

Is the most common objection, and it misreads what's actually being asked for. You don't need the full ceremony. You need the discipline to separate the customer from the product and rank both by importance, which a five-person conversation can do in an afternoon.

"Design already knows the customer"

Is the second, and Nissan's example answers it directly. Confident, well-resourced teams still misfire when they skip the explicit comparison; knowing your customer and proving the fit on paper are different exercises, and only one of them is checkable by anyone outside the room.

"This is a strategy exercise, not a design one"

Is the third. It stops being someone else's problem the moment engineering starts building against the wrong pain reliever. Design either owns the fit-check upfront, or inherits the cost of its absence later, and the second option is always more expensive.

A fit-check, in whichever format you choose, is the cheapest insurance a proposition ever gets. This is also the layer that separates a genuine Product Operating Model from a delivery pipeline that moves fast: not more process, but proof, on paper, that what gets built is what the customer actually needs. Prove the fit before you prove it in production.

Before your next kickoff, ask whether anyone can point to the document that shows which pains and gains this proposition actually solves. If nobody can, that’s where Supply starts. More at designatscale.co/spy.

REFERENCES

• Osterwalder, A., Pigneur, Y., Bernarda, G., Smith, A. (2014) Value Proposition Design: How to Create Products and Services Customers Want, John Wiley & Sons
• Interaction Design Foundation, "What is The Value Proposition Canvas" (CC BY-SA 4.0) — Nissan/Tesla example sourced via secondary material
• Railsware Blog, "Value Proposition Canvas"
• Design at Scale™ Book & Journal (internal)

SUMMARY

• The Value Proposition Canvas requires proof of fit between a customer profile (jobs, pains, gains) and a value map (products, pain relievers, gain creators), each built independently and then compared.
• Nissan’s Leaf illustrates misfit despite strong engineering; Tesla illustrates fit through line-for-line alignment with the same customer profile.
• The real failure isn’t a bad product; it’s never proving in writing which pains and gains the product solves for.
• DaS™’s Proposition Shaping (Customer Research) and Design Shaping (validated personas, prototyped landscape) already require this fit-check; template optional.
• Proving fit on paper is the layer that distinguishes a Product Operating Model from a fast delivery pipeline.

https://www.figma.com/community/file/1304207301838337864/das-proposition-canvas