Module overview: the summit of strategy is vision

Why this module exists here

In module 1 you learned to tell tactics ("doing things right") apart from strategy ("doing the right things"), and you saw that strategy isn't a twelve-month plan or a list of ambitious objectives, but a coherent set of choices about where to play and how to win. You also saw the most expensive point of all: flawlessly executing the wrong strategy doesn't save you — it leaves you just as far from where you wanted to be, only with more effort spent along the way.

That leaves an open question, and it's exactly the one this module answers: if strategy is a set of choices, choices toward where? What do you measure against to decide that one option is better than another? You need something above strategy itself — something that doesn't change every quarter and that gives meaning to every "yes" and every "no" strategy is about to pronounce. That's vision: where the company is headed and why. This module starts, literally, at the top of the stack — the highest of the four layers you're going to learn to tell apart: vision → mission → strategy → tactics.

Connection to module 1. There you learned that "bad strategy" (Rumelt) is often a list of objectives disguised as strategy. Here you're going to see the sibling mistake, one level up: a "vision" that's actually a slogan — pretty, inspiring, and completely useless for deciding anything. Telling a real vision apart from an empty slogan is the first filter for everything that follows in this guide.

An everyday analogy: the North Star

For centuries, sailors used the North Star to orient themselves on the open sea. The North Star has an odd property: you never reach it. It isn't a port, it isn't an island, it isn't a destination you arrive at and disembark. It's a fixed point in the sky that tells you, night after night, whether you're heading north or you drifted off course. The captain doesn't plot tomorrow's journey by looking at the star — they plot tomorrow's journey by looking at the map, the weather, the cargo, and the crew — but each of those tactical decisions gets checked against the same question: does this bring me closer to north, or further away?

That's exactly what a vision does inside a company. It doesn't tell you what to build this quarter — that's the job of strategy and, further down still, tactics. It tells you the direction every choice, sooner or later, gets measured against. A company without a vision isn't lost for lack of a map — it has plenty of maps, in the form of OKRs, roadmaps, and backlogs — it's lost because it has no star: any north works just as well, and so no choice can be defended any better than another.

Now the uncomfortable half of the analogy, the one you're going to see again and again in this module: a North Star that was in every part of the sky at once wouldn't orient anyone. Its usefulness comes, precisely, from being in a single place — from most of the sky not being north. A vision that says "we want to serve everyone, in everything, everywhere" is the equivalent of a GPS that answers "go anywhere" when you ask it for a route: technically it isn't lying, but it's also useless. This is the exact topic of lesson 5, and it's going to reappear in every lesson of this module.

Worked example: is this really a vision?

Before precisely defining what makes a statement a vision (lesson 2), it's worth looking at the problem from the other side: what does something that sounds like a vision but isn't look like? Mercado, the marketplace that runs through this guide, has a real vision, written with intention. And it could also have, like any company, a corporate slogan that sounds similar but says nothing.

To avoid guessing by eye, we build a small model in Node — classifyLayer — that scans a statement for linguistic signals typical of each layer (vision, mission, strategy, or tactics) and returns the one it finds. It's a pedagogical, rule-based model, not an intelligence that "understands" strategy — you'll see it in full in lesson 4 — but it's enough for this module's first question: between these two sentences, which one is really a vision?

function classifyLayer(statement) {
  const text = statement.toLowerCase();
  const signals = {
    tactic: ['launch', 'implement', 'add', 'sprint', 'this quarter', ' q1', ' q2', ' q3', ' q4'],
    strategy: ['we choose', 'instead of', 'we focus on', 'we will invest', 'the next', 'we bet on', 'we win'],
    mission: ['we exist to', 'our mission', 'we help', ' today'],
    vision: ['the world where', 'the place where', 'someday', 'our vision', 'we imagine a'],
  };
  const order = ['tactic', 'strategy', 'mission', 'vision'];
  for (const layer of order) {
    if (signals[layer].some((kw) => text.includes(kw))) {
      return layer;
    }
  }
  return 'unclear';
}

const mercadosVision = 'The world where anyone discovers, on Mercado, what they didn\'t know they wanted.';
const emptySlogan = 'Be the best marketplace in the region.';

console.log('=== Which of these is really a vision? ===\n');
console.log('"' + mercadosVision + '"');
console.log('  -> detected layer:', classifyLayer(mercadosVision));
console.log('');
console.log('"' + emptySlogan + '"');
console.log('  -> detected layer:', classifyLayer(emptySlogan));

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

=== Which of these is really a vision? ===

"The world where anyone discovers, on Mercado, what they didn't know they wanted."
  -> detected layer: vision

"Be the best marketplace in the region."
  -> detected layer: unclear

The first sentence describes a future state of the world — a place where something specific happens (people discover what they didn't know they wanted) — and that's why the model recognizes it as vision. The second sentence sounds like a vision — it has the right tone, the right spirit — but on closer look it describes no state of the world: "be the best" doesn't say best at what, or for whom, or what it would look like if it were true. classifyLayer doesn't label it "bad vision" — it labels it unclear, because it literally finds no signal for any of the four layers. It's a slogan, not a vision, even if it's been on the "our values" slide of a thousand companies. Lesson 6 comes back to this exact case, by name: aspirational vision vs. empty vision.

The module map

Save this route. The whole module descends, one step at a time, from "what a vision is" to "Mercado's real vision, put to the test":

Idea                                        Lesson    Key concept
───────────────────────────────────────────  ────────  ─────────────────────────────────────
What a vision is (and isn't)                 L2        a desired future state, not a plan;
                                                        the 10-25 year horizon
Vision vs. mission                           L3        where we're headed vs. why we exist
                                                        today -- two different questions
The 4 layers, top to bottom                  L4        vision → mission → strategy → tactic,
                                                        and how each constrains the one below
A vision that says NO                        L5        why a useful vision also rules out
                                                        initiatives, not just inspires them
Aspirational vs. empty                       L6        the BHAG that truly orients vs. the
                                                        slogan that rules out nothing
Mercado's vision, in depth                   L7        the complete case: what it includes,
                                                        what it excludes, and why it looks
                                                        10 years out, not 1
───────────────────────────────────────────  ────────  ─────────────────────────────────────
Project: write and test Mercado's            L8        write Mercado's vision and mission,
vision                                                 map the 4 layers, and filter the backlog

The boundary: what does NOT belong in this module

This module answers a specific question: where are we headed, and why? It doesn't answer several neighboring questions, which belong to other modules in this guide or to other guides in the ecosystem:

• "Who is this for, exactly, and what are we compared to the alternatives?" — that's the target segment and positioning, and it's module 3. Here the vision is broad and long-term; choosing today's segment is a more concrete decision, one floor down.
• "What makes us different and better for that segment?" — that's differentiation and value proposition, module 4.
• "What does the competitive landscape look like, and where is the market headed?" — module 5.
• "Which of our advantages are hard to copy?" — the moats, module 6.
• "How do we bring all of this down to a concrete roadmap?" — the strategic filter over the backlog, module 7.
• The North Star metric — the number a product team watches week to week to know if things are going well — is the topic of product-metrics-and-experimentation-guide. Here we work with the strategic North Star: the direction, not the indicator that measures it.
• Prioritizing with RICE or sizing an opportunity remains the territory of product-thinking-for-engineers-guide. This module doesn't compare initiatives by impact or effort — it compares initiatives against a single question: do they belong to this direction or not?

Resources

• Roger Martin, "Decoding the Strategy Choice Cascade" — rogermartin.medium.com/decoding-the-strategy-choice-cascade-475d40555eb1. Roger Martin himself explaining the five cascading choices from Playing to Win, starting with "what is our winning aspiration?" — the equivalent of vision in his framework. In English.
• Richard Rumelt, Good Strategy Bad Strategy — goodbadstrategy.com. The site for the book that names the mistake this module avoids at the vision layer: an inspiring statement that diagnoses nothing and rules out nothing. In English.
• Jim Collins, "BHAG (Big Hairy Audacious Goal)" — jimcollins.com/concepts/bhag.html. The concept from Built to Last (with Jerry Porras) on 10-to-25-year visions that truly orient, in the author's own words. In English.
• Marty Cagan (SVPG), "Product Vision vs. Mission" — svpg.com/product-vision-vs-mission. The exact distinction that opens this module, explained from the product side (not MBA-level business). In English.