Module overview: from the summit to the first concrete choice

Why this module exists here

Module 2 gave you the summit: Mercado's vision — "the world where anyone discovers, on Mercado, what they didn't know they wanted" — and a filter (visionFilter) for knowing whether an initiative belongs to that ten-year direction or not. That's indispensable, but it's still too high up to make a single decision for this week. A ten-year vision doesn't tell you who to show the product to tomorrow, or what to say when they ask "and how is this different from everything else?" You need to drop one more step.

That step has two stairs, and they're this module's entire content. The first: who is this for, exactly — and who is it NOT for? Not "who could, in theory, use it" (that's almost everyone, and an answer like that is useless), but the concrete segment Mercado is going to serve first and best, even if that means serving other, equally real buyers worse, on purpose. The second: once you know who it's for, what are you, in that person's head, compared to everything else they could choose? That's positioning — not a marketing tagline, but the specific category you occupy when someone in that segment thinks "I need something like this."

Connection to module 2. Mercado's vision (curatedDiscovery, localSellerTrust, serendipity) is deliberately broad — it describes a world, not a customer. This module takes that direction and turns it into the first operational decision: out of everyone who buys something, somewhere, every day, who are you going to serve first, and what are you going to tell them you are? You're going to build and run positionFit, the model that answers an uncomfortable question with data, not intuition: does the product serve THIS segment's job better than the alternatives — on the dimensions THAT segment cares about, not the ones you'd like to win on?

An everyday analogy: the right aisle at the supermarket

Walk into any big supermarket and notice how it's organized: it isn't one giant table with ten thousand loose products — it's a series of aisles, each with a sign overhead ("dairy," "personal care," "snacks"), and inside each aisle, specific shelves at eye level for what sells most. A shopper doesn't walk the entire supermarket every time they need something: they walk straight to the right aisle, because they already know, in advance, which category what they're looking for lives in. That organization isn't an accident of the supermarket's architect — it's the most important business decision any brand makes before a single shopper walks through the door: which aisle do I want to live in, and who am I talking to once I'm standing there?

Segment is the answer to "who walks down this aisle?" — not everyone who enters the supermarket, only whoever has that specific need today. Positioning is the answer to "which shelf do I occupy within that aisle, and why does someone pick me and not the brand right next to me?" Notice something that's going to repeat throughout the module: a yogurt brand doesn't compete against the entire supermarket — it competes against the other three yogurt brands on the same shelf, in front of the same shopper, at the same moment of decision. Choosing the wrong aisle (the segment) is a far more expensive mistake than losing to a competitor within the right aisle — and it's exactly the mistake this module teaches you not to make.

Worked example: two buyers, the same product, opposite verdicts

Before building the complete model (lesson 2 onward), it's worth seeing the final result once, without understanding every piece yet. We build positionFit, which compares Mercado against two alternatives — a generic megastore and a local neighborhood shop — but using the importance weights of a specific segment, not a generic "who's better overall" score. We run the same product, the same alternatives, against two different buyers: someone who browses without knowing exactly what they're looking for, and someone who's searching for an exact SKU and just wants the lowest price and the fastest delivery.

// positionFit(target, product, alternatives): evaluates whether `product`
// serves `target`'s job BETTER than the alternatives, using THAT segment's
// importance WEIGHTS -- not a generic "who's better overall" score.
// Winning on a dimension the segment doesn't care about counts for nothing.
function positionFit(target, product, alternatives) {
  const dims = Object.keys(target.weights).filter((d) => target.weights[d] > 0);
  const weightedScore = (c) => dims.reduce((sum, d) => sum + target.weights[d] * c.scores[d], 0);

  const productScore = weightedScore(product);
  const rivals = alternatives.map((a) => ({ name: a.name, score: weightedScore(a) }));
  const bestRival = rivals.reduce((a, b) => (b.score > a.score ? b : a));

  return {
    segment: target.name,
    productWeightedScore: Number(productScore.toFixed(2)),
    bestRival: bestRival.name,
    bestRivalWeightedScore: Number(bestRival.score.toFixed(2)),
    fitsSegment: productScore > bestRival.score,
  };
}

const mercado = { name: 'Mercado', scores: { curatedDiscovery: 9, sellerTrust: 8, catalogBreadth: 6, price: 5, deliverySpeed: 5, convenience: 6 } };
const genericMegastore = { name: 'genericMegastore', scores: { curatedDiscovery: 3, sellerTrust: 4, catalogBreadth: 9, price: 8, deliverySpeed: 9, convenience: 8 } };
const localShop = { name: 'localShop', scores: { curatedDiscovery: 6, sellerTrust: 9, catalogBreadth: 2, price: 4, deliverySpeed: 3, convenience: 3 } };
const alternatives = [genericMegastore, localShop];

const explorers = { name: 'explorers', weights: { curatedDiscovery: 0.4, sellerTrust: 0.3, catalogBreadth: 0.1, price: 0.1, deliverySpeed: 0.05, convenience: 0.05 } };
const exactSkuShoppers = { name: 'exactSkuShoppers', weights: { curatedDiscovery: 0, sellerTrust: 0, catalogBreadth: 0.1, price: 0.35, deliverySpeed: 0.35, convenience: 0.2 } };

console.log('=== Does Mercado serve this job better than the megastore and the local shop? ===\n');
console.log(JSON.stringify(positionFit(explorers, mercado, alternatives)));
console.log(JSON.stringify(positionFit(exactSkuShoppers, mercado, alternatives)));

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

=== Does Mercado serve this job better than the megastore and the local shop? ===

{"segment":"explorers","productWeightedScore":7.65,"bestRival":"localShop","bestRivalWeightedScore":6,"fitsSegment":true}
{"segment":"exactSkuShoppers","productWeightedScore":5.3,"bestRival":"genericMegastore","bestRivalWeightedScore":8.45,"fitsSegment":false}

There's the module's complete result, given away in two lines: the same Mercado, without changing a single line of product, wins for one buyer and clearly loses for the other. For someone who browses (explorers), Mercado scores 7.65 against the best rival (the local shop, at 6) — it wins. For someone searching for an exact SKU (exactSkuShoppers), Mercado scores just 5.3 against the generic megastore, which scores 8.45 — it loses, and not by a little. Nobody changed the product between one run and the other — the only thing that changed was who you're selling it to. That's the module's entire point: the question "is Mercado good?" doesn't have one answer — it has a different answer for each segment, and a real strategy chooses, on purpose, which of those answers to build for.

The module map

Save this route. It descends from "who, in general" to Mercado's verified positioning statement, with data:

Idea                                        Lesson    Key concept
───────────────────────────────────────────  ────────  ─────────────────────────────────────
Who it's for -- and who it's NOT for         L2        the target segment as a choice that
                                                        also excludes real buyers
The beachhead: narrow before wide            L3        Moore -- a beachhead you can win
                                                        entirely, not a continent
The job, not the demographics                L4        Christensen -- the right segment is
                                                        defined by what people are trying
                                                        to achieve, not age/income/location
What positioning IS                          L5        the category you occupy in the mind;
                                                        winning the right attribute, not all
The positioning statement                    L6        the Moore/Dunford template, written
                                                        and verified with positionFit
Repositioning: when, why, and the risk       L7        copying the leader dilutes your real
of copying the leader                                  advantage without reaching theirs
───────────────────────────────────────────  ────────  ─────────────────────────────────────
Project: Mercado's segment and               L8        define Mercado's target segment and
positioning statement, verified                        positioning statement, and run
                                                        positionFit against both alternatives
                                                        to prove it with data

The boundary: what does NOT belong in this module

This module answers two very specific questions: who is this for? and what are we compared to the alternatives? It doesn't answer several neighboring questions, which belong to other modules or other guides in the ecosystem:

• "How do I confirm with real users that this segment exists and that this job matters to them?" — that's discovery, and it's the territory of product-discovery-and-prototyping-guide. Here we work the strategic choice of who to target; validating that choice with interviews and prototypes is a different, later job, with its own tools.
• "What makes us different and better for that segment, beyond serving their job better?" — that's differentiation and value proposition, and it's module 4. This module chooses the aisle and the shelf; module 4 explains what's on that shelf that nobody else has.
• "What does the full competitive landscape look like, and where is the market headed?" — module 5. Here we only use two fixed alternatives (the megastore and the local shop) as a reference for positioning; the full competitive map comes later.
• Prioritizing with RICE what to build first, or sizing an opportunity — remains the territory of product-thinking-for-engineers-guide. positionFit doesn't calculate any initiative's impact or effort — it decides whether the product, as it is today, serves a segment better than the alternatives. It's a prior, different question.
• The job understood as an interview technique or customer process map — this module uses jobs-to-be-done vocabulary (lesson 4) only to precisely choose the right segment at the strategic level, not as a qualitative research methodology.

Resources

• April Dunford, Obviously Awesome: How to Nail Product Positioning so Customers Get It, Buy It, Love It — aprildunford.com/books. This entire module's reference book: the step-by-step process for finding the right segment and category, instead of guessing. In English.
• Geoffrey Moore, Crossing the Chasm — geoffreyamoore.com/book/crossing-the-chasm. The source of the term beachhead that lesson 3 develops in depth: a beachhead small enough to win entirely. In English.
• Clayton M. Christensen and Taddy Hall, "Know Your Customers' Jobs to Be Done" — hbr.org/2016/09/know-your-customers-jobs-to-be-done. The article that names this module's second stair: the segment gets defined by the job people hire the product to do. In English.
• Marty Cagan (SVPG), "Product Market Fit" — svpg.com/product-market-fit. Cagan defends, from the product side, the same idea that opens this module: win one segment at a time, not all at once. In English.