Value proposition design

Source: Value Props: Create a Product People Will Actually Buy, Harvard Innovation Labs, 1:27:29, uploaded 2023-04-01.

A value proposition starts before the pitch. It starts with a specific user, a painful enough problem, and a reason the customer would change behavior now.

Core idea

The session separates three jobs: define the customer and problem, evaluate whether the problem is worth solving, then build a crisp value proposition. The useful discipline is to stop treating an “idea” as the unit of work. An idea only becomes useful when it attaches to a customer problem that is urgent enough to pull a product into the world.

The value proposition is not a slogan. It is a testable claim about who has the pain, why the pain matters, what changes after the product exists, and whether the gain is large enough to beat the cost of switching.

Notes

• Start from the user’s eyes. Do not pitch the idea first; ask until the problem is clear in the customer’s own language.
• Narrow the customer before sharpening the product. A value proposition for “everyone” is usually too vague to test.
• A well-stated problem makes the team easier to align. If the team cannot name the customer and pain point, the product work becomes guesswork.
• The “four U’s” are a useful pressure test: unworkable, unavoidable, urgent, and underserved.
• Unworkable means the current path is materially broken, expensive, slow, risky, or painful.
• Unavoidable means the customer cannot simply opt out. Taxes, aging, health, education, compliance, and infrastructure often create this kind of pressure.
• Urgent means the customer has a reason to act soon, not eventually.
• Underserved means existing options leave a gap in access, quality, cost, fit, trust, or availability.
• A strong value proposition still needs a viable business model. Being loved by a customer does not guarantee the economics work.
• The product is rarely the whole solution. Apps need networks, marketplaces need supply, payments need trust rails, electric cars need charging, and enterprise tools need workflow fit.
• Name the dependencies that must exist for the customer to experience the promised value.
• The “three D’s” evaluate the opportunity shape: disruptive, discontinuous, and defensible.
• Disruptive means the product changes the cost, access, or usage pattern enough to matter.
• Discontinuous means the product enables something that could not be done before.
• Defensible means there is some protection against easy copying: IP, data, network effects, workflow lock-in, brand, partnerships, or accumulated operational advantage.
• The before-and-after exercise is a plain-language test. If the before state does not sound painful and the after state does not sound materially better, the proposition is weak.
• The gain-pain ratio decides adoption. Customers weigh money saved, time saved, risk reduced, status gained, or new capability against search, trial, purchase, training, switching, and ownership pain.
• The best signal is customer pull. If customers keep explaining why they need the change, the value proposition is probably closer to real.
• A minimum viable segment is the smallest customer group with a blatant and critical need, enough similarity to reach them, and enough willingness to change.

Takeaways

• Define the customer before defining the product.
• Use customer interviews to surface pain, not to sell the idea.
• Test the problem with the four U’s.
• Map the whole solution, including dependencies outside the product.
• Make the before-and-after state concrete.
• Treat adoption pain as part of the value proposition.

Related: startup timing, startup funding, marketing as context, blitzscaling.