Module 4: Differentiation And Value Prop

What a value proposition IS (and isn't)

Next →

Description

A value proposition (value prop) is a sentence — one, short, verifiable — that answers: for this specific segment, why choose you and not the usual alternative? It isn't a marketing paragraph, it isn't the "features" section of the product page, and above all it isn't a list of everything the product does. It is, in its strictest form, the sentence spoken out loud that summarizes what lesson 2 already proved with numbers: the dimensions where differentiationMap marked verdict: 'differentiation', and only those.

That last sentence is this lesson's hard rule, and it's worth repeating because it's the one most often broken in practice: every claim inside a value proposition should be auditable against the differentiation map and come out backed. If a claim describes a table-stakes dimension or a gap you lost, it doesn't belong in the value proposition — at most, it belongs in the fine print of the product page.

Connection to the module. Lesson 2 gave you the complete map of where you genuinely win. This lesson adds no new dimension — it takes the same map and turns it into the artifact a real buyer can actually read: a sentence, not a table.

An everyday analogy: a movie's logline

Before a movie gets filmed, someone at the studio reduces it to a single sentence — the logline — that has to convince an executive to invest millions without having seen a single minute of footage. A good logline sounds like this: "A man wakes up with no memory and has to discover who tried to kill him, before they try again." In one sentence you know the genre, the tension, and why this story — and not just any other thriller — is worth watching.

Now imagine that, instead of a logline, someone hands you the full spec sheet: "it has car chases, an award-winning actor, was filmed in six countries, an eighty-piece orchestral score." Every fact is true. None of them tells you why to watch this movie instead of any other action thriller — because car chases, award-winning actors, and orchestral scores are, in the action genre, table stakes: almost any big movie in the genre has them. The spec sheet describes the product; the logline describes the reason to choose it.

A value proposition is your product's logline, not its spec sheet. And the most common mistake when writing one — confusing one for the other — is exactly this lesson's topic.

Worked example: auditing two candidate value propositions for Mercado

Two candidate value propositions come to the table. Before debating which one "sounds better," we audit them against lesson 2's differentiation map — not against anyone's ear.

function differentiationMap(us, competitors, dimensions) {
  const REAL_DIFF_MARGIN = 2;
  return dimensions.map((dim) => {
    const usScore = us.scores[dim.key];
    const rivals = competitors.map((c) => ({ name: c.name, score: c.scores[dim.key] }));
    const best = rivals.reduce((a, b) => (b.score > a.score ? b : a));
    const gap = usScore - best.score;
    let verdict;
    if (gap >= REAL_DIFF_MARGIN) verdict = 'differentiation';
    else if (gap <= -REAL_DIFF_MARGIN) verdict = 'gap';
    else verdict = 'parity';
    return {
      dimension: dim.key,
      mattersToSegment: dim.matters,
      usScore,
      bestCompetitor: best.name,
      bestCompetitorScore: best.score,
      verdict,
    };
  });
}

const mercado = {
  name: 'Mercado',
  scores: { catalogBreadth: 3, price: 3, deliverySpeed: 4, curatedDiscovery: 5, localSellerTrust: 5 },
};
const genericMegastore = {
  name: 'genericMegastore',
  scores: { catalogBreadth: 5, price: 5, deliverySpeed: 4, curatedDiscovery: 2, localSellerTrust: 2 },
};
const neighborhoodShop = {
  name: 'neighborhoodShop',
  scores: { catalogBreadth: 1, price: 3, deliverySpeed: 2, curatedDiscovery: 3, localSellerTrust: 3 },
};
const dimensions = [
  { key: 'catalogBreadth', matters: false },
  { key: 'price', matters: false },
  { key: 'deliverySpeed', matters: true },
  { key: 'curatedDiscovery', matters: true },
  { key: 'localSellerTrust', matters: true },
];
const map = differentiationMap(mercado, [genericMegastore, neighborhoodShop], dimensions);
const verdictOf = (key) => map.find((r) => r.dimension === key).verdict;

// Audits a value proposition: for each claim, looks up its verdict in the
// already-computed map, and counts how many are backed by real
// differentiation (not by parity or by a gap).
function auditValueProp(label, claimedDimensions) {
  console.log(`[${label}]`);
  for (const key of claimedDimensions) {
    console.log(`  - ${key}: ${verdictOf(key)}`);
  }
  const backed = claimedDimensions.filter((key) => verdictOf(key) === 'differentiation');
  console.log(`  -> ${backed.length}/${claimedDimensions.length} claims backed by real differentiation.\n`);
}

console.log('=== Which of these two is a real value proposition? ===\n');
auditValueProp(
  'A: "the biggest catalog, the best prices, and fast delivery"',
  ['catalogBreadth', 'price', 'deliverySpeed']
);
auditValueProp(
  'B: "curated discovery with trusted local sellers"',
  ['curatedDiscovery', 'localSellerTrust']
);

What to expect. Running the file with Node, the output is exactly this:

=== Which of these two is a real value proposition? ===

[A: "the biggest catalog, the best prices, and fast delivery"]
  - catalogBreadth: gap
  - price: gap
  - deliverySpeed: parity
  -> 0/3 claims backed by real differentiation.

[B: "curated discovery with trusted local sellers"]
  - curatedDiscovery: differentiation
  - localSellerTrust: differentiation
  -> 2/2 claims backed by real differentiation.

Candidate A sounds like what many teams write on their first attempt — each claim is individually verifiable ("yes, we deliver in a reasonable time") and even feels generous, because it promises three things instead of one. But audited against the map, all three fail: catalogBreadth and price are gaps Mercado directly loses against the generic giant, and deliverySpeed is table stakes — true, but no different from what any serious rival offers. It's, literally, the movie's spec sheet: true facts, zero real reason to choose this option over the other. 0 of 3.

Candidate B doesn't promise three things — it promises two, and both pass the full audit. It's shorter than A, says fewer things, and yet it's the only one that genuinely answers "why us and not them." That's this lesson's central counterintuition: a value proposition doesn't improve by saying more — it improves by saying only what the map can prove.

Going deeper: the anatomy of a real statement

A complete value proposition, following the classic positioning format (Geoffrey Moore, also popularized by April Dunford), has five parts, in this order:

For [target segment]                     <- from module 3
who [job / unmet need]                   <- from module 3
[product] is a [category]                <- from module 3 (positioning)
that [key differentiator]                <- from this module (differentiationMap)
unlike [main alternative], which [conceded gap]

Applied to Mercado, with each piece citing where it comes from:

For buyers who browse without knowing exactly what they're looking for,
who need to discover something they'll love and trust who's selling it,
Mercado is the curated-discovery marketplace
that connects you with verified local sellers,
unlike the generic giant, which shows you everything but doesn't help
you find anything -- and unlike the neighborhood shop, which you do
know but can't explore beyond its four walls.

Notice something important: the complete sentence does mention, at the end, two things Mercado doesn't have (the giant's catalog or the neighborhood shop's physical closeness) — but it mentions them as what gets conceded on purpose, not as a promise of its own. That's different from candidate A, which presented catalogBreadth and deliverySpeed as if they were Mercado's advantages. Naming what you give up, deliberately, strengthens the value proposition — pretending you win everything weakens it, because the buyer sooner or later finds out on their own.

A quick, brutal test: the "swap test." Take any candidate value proposition and replace the product's name with a direct competitor's. If the sentence still sounds just as true with the name swapped ("genericMegastore has the biggest catalog, the best prices, and fast delivery" — the generic giant could say that too, and in fact would have more grounds to), it wasn't a value proposition: it was a category description. Candidate B fails the swap test for the generic giant and for the neighborhood shop — neither could honestly say "I connect you with verified local sellers" without lying. That's the signal that it's a real value proposition.

Common mistakes

Writing the value proposition as a feature list. What happens: the product document lists eight or ten system capabilities — search, one-click checkout, notifications, favorites, purchase history — and calls it "our value proposition." Why it happens: a long list feels more complete and more honest than a short sentence; it seems like you're "showing all the work." How to spot it: if your "value proposition" has more than two or three central claims, or if it sounds like a product changelog, it isn't a value proposition — it's a feature inventory, and this lesson's worked example showed exactly what happens when that inventory gets audited: most of it doesn't survive. How to fix it: apply auditValueProp to every candidate claim and keep only the ones the map backs as differentiation — usually one or two survive, never eight.

Including a table-stakes dimension presented as a differentiator. What happens: deliverySpeed — tied, per lesson 2 — shows up in the value proposition as if it were an exclusive Mercado achievement. Why it happens: it's a real capability, one real effort was put into, and so it feels deserving of a spot in the sentence that sells the product — without noticing rivals put in the same effort. How to spot it: the exact same check from lesson 2 — compare the score against bestCompetitorScore; if the difference is smaller than the margin, it can't be in the value proposition. How to fix it: move that claim from the value proposition (where it competes for space with real differentiation) to the regular product page, where it can stay true without pretending to be special.

A value proposition that would pass with any name. What happens: the statement sounds professional and well-written, but running the swap test — swapping "Mercado" for any competitor's name — it still sounds just as true. Why it happens: generic sentences like "the best shopping experience" or "quality and trust" are easy to write and hard to object to, precisely because they commit to nothing specific — the same "fluff" problem you saw with vision, in module 2. How to spot it: run the swap test explicitly, with your strongest competitor's name in your product's place, and read the sentence out loud. How to fix it: every claim in the value proposition must name something specific the differentiation map backs — not an adjective ("better," "trustworthy") but a verifiable noun ("verified local sellers," "curated discovery").

Exercises

Exercise 1 — Predict before running. A third candidate, C, proposes Mercado's value proposition resting solely on deliverySpeed (Mercado score = 4, genericMegastore = 4, neighborhoodShop = 2; matters: true). Without running anything, predict what auditValueProp would return for this candidate, and how many of its claims (out of 1) would end up backed.

See solution

The best rival on deliverySpeed is genericMegastore at 4 — the same score as Mercado. The gap is 4 - 4 = 0, within parity's range (neither >= 2 nor <= -2). auditValueProp would report deliverySpeed: parity and 0/1 claims backed by real differentiation. Candidate C fails the audit just like candidate A in the worked example, and for the exact same reason: it rests the entire value proposition on a table-stakes dimension.

Exercise 2 — Apply the swap test. Take this real value proposition from a company (unnamed, so you don't get distracted by the brand): "We offer a fast, secure, and reliable shopping experience, with the best customer service." Mentally swap "we offer" for the name of three different marketplaces you know. Does the sentence still sound just as true with all three? What does that tell you about whether it's a real value proposition?

See solution

The sentence passes — with no change in meaning — with practically any marketplace you can think of, because "fast, secure, reliable, with the best service" names no specific dimension and no verifiable fact: it's the category's entire table stakes, said in adjectives instead of nouns. The fact that the sentence survives the swap test without losing credibility is, precisely, the signal that it isn't a value proposition — it's a description of what any serious player in that category promises, written to sound confident without committing to anything verifiable.

Exercise 3 — Write your own. Using "going deeper"'s five-part template ("For [segment] who [job], [product] is a [category] that [differentiator], unlike [alternative], which [conceded gap]"), write your own version of Mercado's value proposition. Don't copy the worked example's — you can use the same two real-differentiation dimensions (curatedDiscovery, localSellerTrust), but in your own words.

See solution

There's no single correct answer — the exercise evaluates whether you follow the five parts without inventing differentiators outside the map. A reasonable alternative version: "For someone who walks in to shop with no fixed idea of what they're looking for, who wants to feel like they discovered something rather than just checked something off a list, Mercado is the discovery destination where every seller is a real, verified local person with a name — unlike the generic giant, where everything looks equally anonymous, no matter who's selling it." Notice that, just like in the worked example, this version also names what it gives up (the generic giant's "anonymous" feel) instead of pretending to win at everything.

Summary and next step

A value proposition is the one-sentence version of what the differentiation map already proved with numbers — never a list of everything the product does. This lesson's hard rule is that every claim inside it must be auditable and come out marked differentiation, not parity or gap; and the quick test for knowing whether you got there is the swap test: if the sentence still sounds true with a competitor's name in your place, it isn't yours yet.

Before moving on you should be able to: write the five-part template from memory; audit any candidate value proposition against an already-computed differentiation map; and apply the swap test to a real marketing sentence you see this week.

Lesson 4 takes this same value proposition and puts it face to face against a named competitor — the generic giant — to precisely answer the question that gives this guide its title, in its most direct form: why us, and not them?

Resources

← PreviousParity vs. differentiation: table stakes are not an advantageNext →Why us, and not them