Value Proposition
Why can a genuinely better product lose to a worse one that explains itself?
The idea
A value proposition names the customer, problem, outcome, and reason to believe.
In the real world
A payroll tool sells fewer errors and faster close, not software features.
Going deeper
The failure mode is not that people describe features instead of benefits — most know to avoid that. It is that the four parts get compressed until only the ones the seller finds interesting survive: what it does, and why it is clever.
All four have to be present and specific. Naming the customer excludes people, which feels like losing reach and is what makes the rest legible. Naming the problem in their words rather than yours is what makes them recognise themselves. The outcome has to be a changed circumstance, not a capability. And the reason to believe has to be checkable by a sceptic, because an unsupported outcome is just a claim.
Where it stops applying
A value proposition is not positioning. It says why someone should want this; positioning decides what they will compare it against. A strong proposition judged against the wrong reference class still loses.
Why it matters
It forces you to say who is buying, what problem they have, and why they should believe you can fix it, in terms they would recognise.
Try this today
Rewrite an offer as one measurable customer outcome.
Test yourself
A payroll tool's site lists automated tax tables, API access, and a mobile app. A finance manager reads it and leaves. What is missing?
Show the answer
The outcome and the reason to believe it. Features describe what the tool has; the buyer needs to know what changes for them, and what evidence supports that. Nothing on the page names either.
Learn this in the feed Answering from memory, then again days later, is what makes it stick.