Module 2: Vision And Mission

Mercado's vision, in depth

Next →

Description

This lesson brings together everything you learned in the module and applies it, with no shortcuts, to Mercado's complete vision: what it includes, what it excludes, and — the topic that was still missing a thorough explanation — why its horizon is years, not quarters. You already know how to recognize a vision (lesson 2), separate it from mission (lesson 3), place it among the four layers (lesson 4), use it to rule out initiatives (lesson 5), and tell an aspirational version apart from an empty one (lesson 6). What's left is watching it withstand the hardest test of all: a bet that looks great this quarter, but betrays the ten-year direction.

Connection to the module. This is the lesson that closes the content loop before the project. It introduces no new concept — it gathers the ones you already have and puts them to work together, on the full case, with a twist: until now visionFilter evaluated time-neutral initiatives (features that simply fit or didn't). Here you apply it to initiatives that are tempting precisely because they promise a quick win — the kind of decision where a real vision, with a long horizon, has to do its hardest job: say no to something that shines today, in the name of something worth more in ten years.

An everyday analogy: the oak tree nobody watches grow

There's a gardening saying that sums up the horizon problem: "the best time to plant an oak tree was twenty years ago; the second-best time is today." An oak takes decades to give real shade. Whoever plants it knows, for certain, they're not going to sit under that shade — maybe their children will. And yet, every season, there's a real temptation: instead of the oak, plant something fast-growing that shows visible results in weeks. Vines that climb and bloom almost immediately, plants that "fix" an empty corner of the garden in a weekend.

The problem isn't that those fast plants are bad on their own — many of them, in fact, aren't, in the right spot. The problem is that a gardener who fills their entire garden with fast-growing plants, season after season, because each one "looks great right now," ends up with a garden that never gives the oak's deep shade — and worse: some of those fast plants, the invasive ones, end up choking out the oak that was actually growing slowly in the same ground. The long horizon doesn't mean "plant nothing this season" — it means choosing, season after season, what serves the oak, even when something flashier is competing for the same space and the same budget.

Mercado has its own oak: a ten-year-or-more vision, of a world where shopping starts with discovering. And, like any gardener, every quarter fast-growing plants show up — aggressive promotions, huge generic catalogs, price wars — that promise visible numbers right away. This lesson is about recognizing which of those fast plants actually help the oak (water it, don't steal its light) and which ones are choking it without anyone noticing yet, because the damage from a choked oak takes years to show.

Worked example: tempting bets, evaluated against ten years

Let's take three initiatives a growth team would propose in any quarterly review — all three promise fast, measurable results — and run them against Mercado's complete vision with visionFilter, the same model from lesson 5.

function visionFilter(vision, initiatives) {
  return initiatives.map((initiative) => {
    const brokenExclude = vision.excludes.find((rule) => initiative.conflictsWith.includes(rule));
    const matchedInclude = vision.includes.find((rule) => initiative.supports.includes(rule));
    let fitsVision;
    let reason;
    if (brokenExclude) {
      fitsVision = false;
      reason = `conflicts with something the vision rules out: "${brokenExclude}"`;
    } else if (matchedInclude) {
      fitsVision = true;
      reason = `serves something the vision includes: "${matchedInclude}"`;
    } else {
      fitsVision = false;
      reason = 'does not connect with any "yes" in the vision';
    }
    return { initiative: initiative.name, fitsVision, reason };
  });
}

const mercadosVision = {
  statement: 'The world where anyone discovers, on Mercado, what they didn\'t know they wanted.',
  includes: ['curatedDiscovery', 'localSellerTrust', 'serendipity'],
  excludes: ['exactSkuSearchEngine', 'lowestPriceRace', 'genericMegastore'],
};

// Three bets that look tempting for their short-term gain, evaluated
// against a vision that looks 10 years ahead, not one quarter.
const temptingBets = [
  { name: 'curatedSeasonalCollections', supports: ['curatedDiscovery'], conflictsWith: [] },
  { name: 'sameDayFlashDiscountsEveryday', supports: [], conflictsWith: ['lowestPriceRace'] },
  { name: 'bulkWholesaleCatalog', supports: [], conflictsWith: ['genericMegastore'] },
];

console.log('=== Tempting short-term bets, vs. a 10-year vision ===\n');
const results = visionFilter(mercadosVision, temptingBets);
for (const r of results) {
  console.log(`${r.initiative}: fitsVision=${r.fitsVision} (${r.reason})`);
}

const inCount = results.filter((r) => r.fitsVision).length;
console.log(`\n${inCount}/${temptingBets.length} survive the long-term vision filter.`);

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

=== Tempting short-term bets, vs. a 10-year vision ===

curatedSeasonalCollections: fitsVision=true (serves something the vision includes: "curatedDiscovery")
sameDayFlashDiscountsEveryday: fitsVision=false (conflicts with something the vision rules out: "lowestPriceRace")
bulkWholesaleCatalog: fitsVision=false (conflicts with something the vision rules out: "genericMegastore")

1/3 survive the long-term vision filter.

Think about the business case each of these three would bring to a quarterly review. sameDayFlashDiscountsEveryday (daily flash discounts) would probably bring a sales chart trending up the week of launch — a real, visible result, easy to defend in front of any board. bulkWholesaleCatalog (generic wholesale catalog) would probably bring an immediate jump in the total number of listed products, another metric that goes up and looks good on a slide. Neither is a bad idea in general — they are, literally, the fast-growing vine: they show visible results, now.

The problem, and it's exactly what visionFilter is designed to expose, is that both clash with explicit excludes from the vision: aggressively competing on price (lowestPriceRace) and turning into a generic everything-for-everyone catalog (genericMegastore). Accepting either one — just because the quarter's chart looks good — is exactly the moment the oak starts losing light to the vine, without anyone noticing until it's already grown too much. Only curatedSeasonalCollections (seasonally curated collections) serves both the quarter's result and the ten-year direction at the same time — and that combination, when it exists, is the best possible signal of a good bet.

Going deeper: why Mercado's horizon is years, not quarters

Recall lesson 4's speed table: vision barely changes, precisely because its horizon is far longer than any individual business decision's. Applied to Mercado specifically:

  • A quarter is enough to ship a feature (tactics) — the recommendations feed redesign, for example.
  • One to three years is enough to execute a full strategy — building the relationship with trusted local sellers until it's a real differentiator, not just a promise on the "About us" page.
  • Ten years or more is what it takes for "discovering becomes more natural than searching" to stop being an aspirational sentence and become the actual shopping habit of millions of people — a behavior change at that scale doesn't happen in a single launch, it happens through an accumulation of thousands of consistent decisions, quarter after quarter, all pointing in the same direction.

This doesn't mean the long horizon justifies inaction today — that would be the mistake of believing planting an oak means doing nothing while it grows. It means the opposite: every quarter, Mercado keeps shipping features, keeps measuring results, keeps responding to competitors — but each of those short-term decisions gets filtered first against the ten-year question, not the other way around. The long horizon doesn't compete with short-term execution; it directs it.

Common mistakes

Sacrificing the vision under quarterly-results pressure. What happens: a rough patch of numbers hits — slower-than-expected growth, an aggressive competitor cutting prices — and leadership approves, "just this once," an initiative that clashes with the vision (a price war, a generic catalog) to recover the quick number. Why it happens: the pressure of a bad quarter is immediate and visible; the cost of betraying the vision is diffuse and takes years to show — exactly like the choked oak, whose damage isn't seen until much later. How to spot it: if an initiative's justification is "just this quarter" or "just for this number," and that initiative clashes with a vision exclude, you already lost the argument before starting — "just this once" almost never is. How to fix it: treat every vision exclude as a line that doesn't get crossed even under pressure, not as a preference that gets negotiated when the numbers get tight. If it genuinely needs crossing, that isn't a tactical exception — it's a sign the vision itself needs reviewing (rare, but possible), and that's a different, much more serious conversation.

Confusing "long horizon" with "don't act now". What happens: the ten-year vision gets used as an excuse for not committing to any result this quarter — "we're playing the long game" becomes the answer to any uncomfortable question about why this month's number didn't move. Why it happens: it's more comfortable to appeal to a distant, unverifiable horizon than to be accountable for a concrete short-term result. How to spot it: if "we're thinking long-term" never comes paired with a concrete tactic this quarter that serves that vision, the phrase is an excuse, not a strategy. How to fix it: remember curatedSeasonalCollections from the worked example — a real short-term bet, with a measurable result this season, that also serves the ten-year oak. The long horizon gets fulfilled through consistent short-term decisions, not through the absence of them.

Changing the vision every time new external pressure shows up. What happens: a new investor, a new board advisor, or an unexpected competitor proposes "rethinking the vision" every few months, and the company rewrites it to accommodate the latest conversation. Why it happens: the vision, having no clear day-to-day owner (unlike the roadmap), is easy to touch without anyone feeling like they're breaking something operational. How to spot it: if you can recall more than one version of "our vision" over the last two years, and the versions say substantially different things (not just better-worded), the vision is being used as a strategy with a pompous name — lesson 2's exact mistake. How to fix it: apply lesson 4's test — "would this still be true in a year, no matter what?" — before accepting any change to the vision. If the answer depends on who's in the room this week, it isn't a vision revision: it's noise.

Exercises

Exercise 1 — Predict before running. Without running anything, for this fourth tempting bet, predict what visionFilter would return against the worked example's Mercado vision:

const fourthBet = {
  name: 'verifiedLocalArtisanProgram',
  supports: ['localSellerTrust', 'curatedDiscovery'],
  conflictsWith: [],
};
See solution

fitsVision: true, with reason: 'serves something the vision includes: "curatedDiscovery"' (the first include in the list that appears in supports, per the order vision.includes.find() walks through them). A verified local artisan program connects to two includes at once — local trust and curated discovery — and conflicts with no exclude. It's, like curatedSeasonalCollections, the kind of bet that serves the ten-year oak and a result measurable this very quarter (more verified sellers, more trust reported by buyers) at the same time.

Exercise 2 — Name the equivalent in your own context. Think of a project or initiative from your own work (or from a company you know) that was, at the time, a "fast-growing plant" — something that produced a visible short-term result but that, looking back, didn't serve (or even hurt) the project's long-term direction. Describe it in 2-3 sentences, naming which implicit exclude it violated.

See solution

There's no single answer — the exercise evaluates whether you can apply the module's vocabulary to a real case. A reference example: a team that, to hit a quarterly active-users target, launches aggressive push notifications that do raise the number that week, but violate (without ever formally naming it) an implicit "don't annoy the user to inflate metrics" exclude — and months later, uninstall rates rise and brand trust drops, a cost that never showed up on the chart that celebrated the launch.

Exercise 3 — Defend the oak in front of the board. Imagine you're in the meeting where sameDayFlashDiscountsEveryday (daily flash discounts) is proposed to recover this quarter's growth. Write, in 3-4 sentences, the argument you'd give to reject it, without sounding like you're against every short-term result (remember this lesson's second common mistake).

See solution

A reasonable argument: "I understand the pressure this quarter, and I'm not against moving the number — in fact, we have an option on the table that also moves it: the seasonally curated collections. The difference is that daily flash discounts clash directly with something our vision explicitly rules out: we don't compete on price, we compete on discovery. If we approve them 'just this quarter,' we start building the reputation of a deals store, not a discovery destination — and that reputation is much harder to reverse than any number from this quarter. I propose we chase the same result with the option that serves both horizons at once."

Notice the structure: it doesn't reject the need for a short-term result (avoiding the second common mistake), names the specific exclude being violated, explains the long-term cost in concrete terms (reputation, not just "the vision"), and offers a real alternative that does pass the filter — the same honest-argument pattern you saw in lesson 5's exercise 3.

Summary and next step

Mercado's vision — the world where you discover what you didn't know you wanted — has a horizon of years, not quarters, and that long horizon isn't an excuse for inaction: it gets fulfilled through consistent short-term decisions, filtered first against the long-term direction. You saw visionFilter applied to three genuinely tempting bets — each with a real short-term business case — and you saw that only one of the three serves both this quarter's result and the ten-year oak at once.

Before moving on you should be able to: explain why a ten-year horizon doesn't mean "don't measure anything this quarter"; and recognize, in a real proposal, the difference between a short-term bet that waters the oak and one that chokes it without it showing yet.

With this the module's six content lessons come to a close. Lesson 8 — the mini-project — asks you to bring it all together: write and evaluate Mercado's vision and mission, map the four layers with a concrete example, and filter a complete backlog against the vision, using the two models you built throughout the module.

Resources

← PreviousAspirational vision vs. empty visionNext →Mini-project: Mercado's vision and mission one-pager