Module 4: Differentiation And Value Prop

Why us, and not them

Next →

Description

So far you've compared Mercado against two rivals at once, dimension by dimension, and then reduced the result to a single sentence for the buyer (the value proposition). This lesson does something more uncomfortable, and more useful to have ready: it puts Mercado face to face against a single, named competitor — the generic giant — and demands a specific answer to the question that names this entire guide: why us, and not them?

It isn't the same question as "how are we different?" (lesson 2) or "how do we say it in one sentence?" (lesson 3). It's the question a skeptical buyer, an investor, or your own boss is going to ask you at some point, pointing at a specific rival: "why would I choose this and not what everyone already uses?" Answering "because we're better" isn't an answer — it's, at most, the headline of an answer you haven't given yet.

Connection to the module. Lessons 2 and 3 worked with Mercado compared against two rivals at once (the generic giant and the neighborhood shop), which is correct for mapping the whole terrain, but it dilutes the "why us" question when the real conversation is, almost always, against a single named rival. This lesson isolates that comparison.

An everyday analogy: the interview with the other candidate in the room

Imagine a job interview where, without meaning to, you know exactly who the other final candidate for the same position is — you worked together before, or someone just told you. If the interviewer asks why they should choose you, there are two possible ways to answer. The first: "I'm like him, but better." That answer gives the interviewer nothing to write down on their decision sheet — better at what? Compared how? It sounds like something you'd say without really knowing what sets you apart.

The second way: "He has three more years of experience than I do, and that's true — I'm not going to say otherwise. But I've already built, end to end, a system the exact size you need solved this year, and he's never done it at that scale." This answer names the rival, admits where the other candidate wins (the years of experience), and precisely names the one thing that genuinely matters for this specific job. It's exactly the same move you're going to practice in this lesson, applied to a product instead of a career: name the rival, admit their real advantages, and point precisely to yours.

Worked example: Mercado, face to face with the generic giant

We leave the neighborhood shop out for a moment — this comparison is exclusively against the rival that dominates the category by volume: the generic giant. Let's run differentiationMap with a single competitor.

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 dimensions = [
  { key: 'catalogBreadth', matters: false },
  { key: 'price', matters: false },
  { key: 'deliverySpeed', matters: true },
  { key: 'curatedDiscovery', matters: true },
  { key: 'localSellerTrust', matters: true },
];

console.log('=== "We\'re like the generic giant, but better" -- better at what, exactly? ===\n');
const results = differentiationMap(mercado, [genericMegastore], dimensions);
for (const r of results) {
  console.log(`${r.dimension}: us=${r.usScore} vs. ${r.bestCompetitor}=${r.bestCompetitorScore} -> ${r.verdict}`);
}

const whyUs = results.filter((r) => r.verdict === 'differentiation');
console.log(`\n"Why us and not them", by name: ${whyUs.map((r) => r.dimension).join(', ')}.`);

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

=== "We're like the generic giant, but better" -- better at what, exactly? ===

catalogBreadth: us=3 vs. genericMegastore=5 -> gap
price: us=3 vs. genericMegastore=5 -> gap
deliverySpeed: us=4 vs. genericMegastore=4 -> parity
curatedDiscovery: us=5 vs. genericMegastore=2 -> differentiation
localSellerTrust: us=5 vs. genericMegastore=2 -> differentiation

"Why us and not them", by name: curatedDiscovery, localSellerTrust.

This is the complete answer to the title's question, and it has three parts, not one. We lose on catalogBreadth and price — the generic giant has more products and lower prices, and there's no honest way to say otherwise. We tie on deliverySpeed — both deliver at a similar pace, so that dimension decides nothing between the two. And we win — with a real margin, not by a lucky point — on curatedDiscovery and localSellerTrust. The complete answer to "why us and not the generic giant?" isn't "because we're better": it's "because for someone who browses without knowing what they're looking for, we help you discover it and you trust who's selling it to you — something they, with all their catalog, don't do. Yes, they have more products and a better price; for the buyer we're targeting, that isn't what decides."

Going deeper: the complete argument, in three moves

Any serious "why us and not them" argument — in front of an investor, a skeptical buyer, or your own team doubting the strategy — needs the same three moves, in this order, and skipping any one of them weakens it:

  1. Name the rival, by name. "The competition" isn't a rival — it's an abstraction that can't be compared against anything. "The generic giant" is: it has scores, it has a map, you can win or lose against it on concrete dimensions.
  2. Admit, first, where the rival wins. Before saying where you win, say where they win — catalogBreadth and price, in this case. This doesn't weaken your argument: it makes it credible. An argument that says "we beat them at everything" sounds like marketing; one that says "they win here, and that's fine, because it isn't what decides" sounds like someone who did the homework.
  3. Name the real differentiation, with the number behind it. Not "we're better at discovery" — "we beat them by a full three points on curated discovery, measured against the same criterion, for the buyer we're aiming to serve." The number isn't there to impress: it's what separates a claim from a proof.

Notice that the second move — admitting the losses — is the one almost everyone skips under pressure, and it's exactly the one that builds the most credibility. A "why us" argument that admits no weakness against the rival doesn't sound confident: it sounds like you didn't do the comparison seriously.

Common mistakes

Saying "we're like X, but better" without naming at what. What happens: the sentence shows up, almost verbatim, in a presentation or a sales conversation — it sounds confident, it sounds like the comparison was already done, and yet it says absolutely nothing verifiable. Why it happens: it's easier to say than to prove, and "better" is a word nobody asks you to define on the spot — until someone does, and the answer isn't ready. How to spot it: any sentence with the structure "we're like X but better/faster/easier" that isn't immediately followed, in the same sentence or the next, by a named dimension and a number, is the empty version. How to fix it: never use that construction without immediately completing it with differentiationMap's result — "we're like the generic giant, but on curated discovery we beat them by a full three points, where they beat us by two on catalog."

Comparing against "the competition" instead of a named rival. What happens: the differentiation argument gets built against an imaginary, averaged rival — "the competition" — instead of against the generic giant or the neighborhood shop, the two real rivals module 3 already identified. Why it happens: talking about "the competition" in the abstract avoids the uncomfortable work of admitting, by name, where a specific rival is better. How to spot it: if your differentiation argument never mentions a real competitor's name, it can't be audited — there's no bestCompetitorScore to verify the claim against. How to fix it: always run differentiationMap against a named competitor, one at a time if needed (as in this lesson), never against a blurry average of "the market."

Ignoring where the rival wins, to avoid weakening the argument. What happens: the "why us" presentation only shows the dimensions where Mercado wins (curatedDiscovery, localSellerTrust) and completely omits catalogBreadth and price, where it clearly loses. Why it happens: showing only wins feels stronger — admitting a loss seems like it would weaken the whole argument. How to spot it: if your "why us" argument has 100% won dimensions, you're probably showing only part of the map, not the whole map — nobody wins at everything, and an argument that claims to loses credibility the moment someone asks about price. How to fix it: follow "going deeper"'s three moves in order — admit first, win after. It's, almost always, more persuasive than hiding the losses.

Exercises

Exercise 1 — Predict without running the code. Only against the generic giant (without the neighborhood shop), add the dimension appAnimationPolish (how polished the app's animations are): Mercado = 5, genericMegastore = 2, and this dimension does not matter to the segment (matters: false). Predict the verdict, and explain why — even though the verdict favors Mercado — this shouldn't show up in a "why us" argument.

See solution

The gap is 5 - 2 = 3, which satisfies gap >= REAL_DIFF_MARGIN (with margin 2), so the verdict is 'differentiation'. However, mattersToSegment is false: Mercado's browsing buyer doesn't choose a marketplace by how polished its animations are. Even though the number says "we win," this isn't a valid "why us" argument — it's exactly the kind of case lesson 7 examines in depth: winning on something nobody cares about feels like a victory, but it moves no purchase decision.

Exercise 2 — Fix an empty pitch. A teammate says, in a meeting: "We're like the generic giant, but much easier to use." Using this lesson's map, rewrite that sentence so it's specific and verifiable — without inventing any dimension not on the map.

See solution

A reasonable rewrite: "We don't compete with the generic giant on catalog or price — they win there, and it isn't our turf. Where we do beat them, with a real margin, is on discovery: we help you find something you didn't know you were looking for, and you trust who's selling it to you, because they're verified local sellers. 'Easy to use' isn't the right dimension — the right dimension is 'helps you decide,' and that's where we're genuinely ahead." Notice the rewrite replaces the vague adjective ("easier to use," which isn't even a dimension on the map) with the two real dimensions that did pass the audit.

Exercise 3 — Get ready for the hard question. Think of the product or project you work on (or one you know well). Name its strongest rival, by name. Without needing exact scores, name in one sentence each of the three moves from "going deeper": (1) the rival, (2) a dimension where the rival honestly wins, and (3) a dimension where you win with a real margin and it matters to your segment.

See solution

There's no single answer — the exercise evaluates whether you can apply the three-move structure to your own case, honestly, about where you lose. The sign you did it well: if your answer to point 2 felt uncomfortable to write, it's probably honest — the discomfort of admitting a real loss is, paradoxically, proof that point 3 (where you win) is also real and not just wishful thinking.

Summary and next step

"Why us and not them" doesn't get answered with "because we're better" — it gets answered by naming the rival by name, admitting first where they honestly win, and then naming the real differentiation, with the number behind it. Against the generic giant, specifically, Mercado's complete answer has three parts: we lose on catalog and price (on purpose, not out of weakness), we tie on delivery speed, and we win with a real margin on curated discovery and local seller trust.

Before moving on you should be able to: identify, in any pitch you hear, whether it follows the three moves or stays at "we're better"; and rewrite an empty pitch into a specific one, using an already-computed differentiation map.

Up to here, the module assumed today's differentiation stays differentiation tomorrow. Lesson 5 breaks that assumption: how fast can a rival copy exactly what makes you win today, and what happens to your "why us" argument when that happens?

Resources

  • April Dunford, "Your Differentiated Value Should Drive Your Pitch" — businessofsoftware.org/talks/your-differentiated-value. On why a sales or product pitch has to rest on verifiable differentiation and not on generic superlatives — this lesson's central topic, in the voice of Obviously Awesome's author. In English.
  • Roger Martin, "Why the How-to-Win Strategy Choice Is So Hard" — rogermartin.medium.com/why-the-how-to-win-strategy-choice-is-so-hard-8de222d62f5c. On the temptation to believe "doing the same as everyone, but with more effort" amounts to a real theory of why you win — this lesson's exact empty-pitch mistake. In English.
  • Michael Porter, "What Is Strategy?" — hbr.org/1996/11/what-is-strategy. The classic article on why competing to be "the best" in the abstract (instead of choosing a specific set of activities different from the rival's) almost never sustains a real advantage. In English.
← PreviousWhat a value proposition IS (and isn't)Next →Sustainable differentiation: how fast you can be copied