Lesson 7: Value Proposition

Last lesson ended with a validated job: field staff need a way to guarantee a safety inspection gets recorded and eventually synced, regardless of momentary connectivity. Knowing the job is only half of the work. The other half is answering a much sharper question: why should this specific person choose this specific product, over every other way — including doing nothing — of getting that job done? That answer is a value proposition, and most product teams either skip articulating it explicitly, or write one so vague it could describe any competitor equally well.

A value proposition is a clear statement of the specific value a product delivers to a specific audience, for a specific job, better than the available alternatives. It is not a slogan, not a mission statement, and not a list of features. It is closer to a hypothesis: "for this person, doing this job, our product is the best available choice, because of these specific reasons, and here is the evidence."

This lesson matters because a fuzzy value proposition produces fuzzy prioritization. If a team cannot state precisely why a customer chooses them over the alternative — a competitor, a workaround, or non-consumption from Lesson 6 — then every roadmap debate becomes a matter of opinion, because there is no shared, falsifiable claim to test decisions against. A sharp value proposition, by contrast, becomes a filter: any proposed feature can be checked against it directly — does this strengthen the specific value we claim to deliver, or is it unrelated, or worse, does it dilute it by pulling the product toward being a slightly-worse version of some other product's value proposition?

Learning Objectives

1
Define a value proposition and distinguish it from a mission statement, a tagline, and a feature list.
2
Construct a value proposition using a structured template that ties a specific audience, job, and differentiator together.
3
Explain why a value proposition must be written differently for divergent user and customer audiences (per Lesson 5), when applicable.
4
Apply the "value proposition as a filter" technique to evaluate whether a proposed feature strengthens or dilutes a product's core claim.
5
Identify the specific failure pattern of a "trying to be everything to everyone" value proposition, and explain why it is a strategic weakness rather than a strength.

Lesson 5 (Users vs. Customers) and Lesson 6 (Jobs To Be Done). This lesson assumes you can name a specific stakeholder role on the Alignment Spectrum and can produce a laddered job statement using the "When/I want to/so I can" structure — a value proposition is, in a real sense, the answer to "and this product is the best way to do that, because..." appended directly onto a job statement.

The Core Definition

A value proposition states: for [a specific audience], who [has a specific job to be done or problem], [this product] is [a specific kind of solution] that [delivers a specific, differentiated benefit], unlike [the primary alternative].

This is a widely used structural template (closely related to Geoffrey Moore's positioning statement format from Crossing the Chasm), and every clause in it is load-bearing:

A specific audience — not "everyone," but a named segment, ideally tied to a specific job (Lesson 6) or a specific position on the Alignment Spectrum (Lesson 5).
A specific job or problem — the thing this audience is actually trying to accomplish, stated in job terms rather than feature terms.
A specific kind of solution — the category the product belongs to, which sets the audience's basic expectations.
A specific, differentiated benefit — the part that actually does the strategic work: what does this product deliver that the alternative does not?
The primary alternative — explicitly named, because a value proposition that doesn't name what it's better than cannot actually be evaluated as a comparative claim at all.

Why "For Everyone" Is Not a Value Proposition — It's the Absence of One

A recurring failure mode, especially at early-stage companies eager not to turn away any potential customer, is a value proposition that tries to serve every possible audience and every possible job simultaneously: "Our platform helps businesses of all sizes work more efficiently." This statement is not wrong, exactly — it is simply not a value proposition, because it fails the basic test of specificity: it says nothing that a hundred other tools could not equally claim, and it gives a PM no way to evaluate whether a proposed feature strengthens or weakens the product's actual position.

This connects directly to a well-established idea in strategy: a real strategic choice necessarily excludes some options in favor of others. A value proposition that includes everyone and excludes nothing has not made a choice, and a product built to satisfy an unbounded audience with an unbounded set of jobs will tend to drift toward being a mediocre, generic version of many other products, rather than an excellent, differentiated version of one thing for one clearly named audience.

The Relationship Between Value Proposition and Job to Be Done

A value proposition is not a replacement for a job statement — it is built directly on top of one. Recall Lesson 6's structure:

Job statement: "When [situation], I want to [motivation], so I can [outcome]."

A value proposition adds a claim about why this specific product is the best available way to satisfy that job:

Value proposition: "For [the person in that situation], [product] is the [category] that [uniquely delivers X], unlike [the alternative they'd otherwise use]."

Written this way, it becomes clear that a value proposition without a preceding, validated job statement is built on sand — it is a claim about being the best solution to a problem the team may not have actually confirmed is real, painful, or currently poorly served (the non-consumption question from Lesson 6). This is why this lesson sits directly after Jobs to Be Done in the curriculum sequence, rather than before it.

Value Propositions Across the User-Customer Divide

Recall from Lesson 5 that users and customers frequently have different jobs and different concerns. A product with meaningful user-customer divergence often needs two distinct value propositions — one aimed at the user, one aimed at the customer/buyer — that are consistent with each other but not identical.

For example, a workplace analytics tool might have:

User-facing value proposition: "For managers who need a quick pulse on team workload, [Product] is the dashboard that surfaces the one metric that matters before your Monday stand-up — unlike digging through three separate spreadsheets."
Customer/buyer-facing value proposition: "For HR leaders who must demonstrate measurable productivity gains to the board, [Product] is the analytics platform that provides audit-ready reporting in one click — unlike stitching together exports from disconnected tools."

Notice these are not contradictory — both could be true of the same underlying product — but they emphasize entirely different benefits, because they answer entirely different jobs held by entirely different people (Lesson 5's Stakeholder Ledger applied directly). A PM who writes only one value proposition and assumes it covers both audiences risks producing marketing, onboarding, and even feature-prioritization decisions that resonate with one side of the Alignment Spectrum and fall flat with the other.

Using a Value Proposition as a Prioritization Filter

Beyond external communication, a value proposition's most important internal use is as a filter for evaluating proposed work. Given any proposed feature, a PM can ask:

Does this feature strengthen the specific, differentiated benefit named in our value proposition?
Does this feature address the named audience and named job — or does it serve a different audience or job entirely?
Does this feature help us win specifically against the named alternative — or is it a feature the alternative already has, making it table stakes rather than differentiation?

A feature can pass a naive "is this valuable?" test while failing this filter — it might be valuable to someone, just not to the specific audience and job the value proposition names, meaning building it doesn't advance the product's actual strategic position; it just adds scope.

Common Mistakes to Avoid

Writing a value proposition that lists features instead of benefits

"Our app has push notifications, calendar sync, and offline mode" describes what the product does, not why a specific person should choose it over an alternative to accomplish a specific job. Features are means; a value proposition is about the end result the audience gets.

Naming no alternative

A value proposition that never says "unlike X" cannot actually be evaluated as a comparative claim, and often signals the team hasn't done the competitive or non-consumption analysis from Lesson 6 needed to write a real one.

Confusing a value proposition with a company mission statement

"We believe in empowering people to do their best work" is an aspirational statement about company purpose, not a specific, falsifiable claim about audience, job, and differentiated benefit. Both can coexist, but they serve different purposes and should not be substituted for each other.

Writing one value proposition when the product genuinely serves divergent user and customer audiences

As shown above, a product with meaningful Alignment Spectrum divergence often needs two coherent, consistent, but distinct value propositions, not one generic statement meant to satisfy both.

Treating "trying to serve everyone" as inclusive or growth-friendly, rather than as a strategic weakness

Broadening a value proposition to avoid excluding any potential customer feels safe, but it removes the specificity that makes the proposition useful as a filter at all, and tends to produce a product that is a diluted, less-differentiated version of several other products' actual value propositions.

Value Proposition