What a vision is (and isn't)

Description

A vision is the description of a future state of the world the company seeks to create — not a plan for getting there, not a list of this year's goals, and not a number you want to hit. It's the answer to a single question: if we succeeded completely, a long time from now, what would the world look like, different because of us? Notice what that question does NOT ask: it doesn't ask how it gets achieved (that's strategy), it doesn't ask what gets built this quarter (that's tactics), and it doesn't ask why the company exists today (that's mission, the topic of lesson 3). It asks, only, to describe the destination.

A vision's horizon is long on purpose — typically between 10 and 25 years, per the Jim Collins and Jerry Porras framework you'll see in lesson 6 — because its job isn't to guide the next release, but to survive several strategy changes without becoming obsolete. A company can change strategy every year or two (new markets, new competitors, new technology) and keep pursuing exactly the same vision. If your "vision" changes every time the roadmap changes, it wasn't a vision — it was a strategy with a pompous name.

Connection to the module. Lesson 1 left you with the open question this entire module answers: if strategy is a set of choices, choices toward what? This lesson gives the first half of the answer precisely: vision is the future state those choices pursue. It doesn't yet compare vision with mission (lesson 3), nor break down all four layers (lesson 4) — here the only job is learning to recognize a real vision when you see one, and to rule out the two most common impostors: the empty slogan and the goal disguised as a vision.

An everyday analogy: the photo of the finished building

Before building a building, an architect produces two very different things, even though at first glance both look like "about the building." The first is a render: an image of what the finished building will look like, with people walking through the lobby, light coming through the windows, the garden already grown in. That image says nothing about cranes, foundations, construction schedules, or cement suppliers. It describes a state of the world that doesn't exist yet, with enough detail that anyone — the client, the bank lending the money, the neighbor who's going to live next door — immediately understands what's being built and why they'd care.

The second thing the architect produces is the construction blueprints: dozens of technical pages on structure, electrical wiring, plumbing, materials. The blueprints are indispensable — without them nobody builds anything — but they don't orient anyone outside the trade. A blueprint doesn't excite you or tell you whether it's worth living there; it tells you how, not what or why.

A company vision is the render, not the blueprints. It describes the finished world — "the place where anyone discovers what they didn't know they wanted" — without yet specifying the structure, the schedule, or the budget. That comes later, layer by layer: mission explains why the architect gets up today to build (lesson 3), strategy chooses what gets built first and with what materials (lesson 4), and tactics is this week's work on the site. Confusing vision with the blueprints — asking it to explain the "how" — is the most common mistake when writing one, and it's exactly what you're going to learn to spot in this lesson.

Worked example: three candidates for "Mercado's vision"

Let's go back to the classifyLayer model from the previous lesson, now with three candidates instead of two, to see more precisely what separates a real vision from its two most common impostors.

// A pedagogical, rule-based model: it looks for linguistic signals typical
// of each layer (vision, mission, strategy, tactic). It doesn't "understand"
// the statement -- it recognizes the vocabulary each layer tends to speak in.
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 candidates = [
  { label: 'Real vision', text: 'The world where anyone discovers, on Mercado, what they didn\'t know they wanted.' },
  { label: 'Empty slogan', text: 'Be the best marketplace in the region.' },
  { label: 'Goal disguised as vision', text: 'We are going to build the industry\'s largest catalog, with more than 50 million products.' },
];

console.log('=== Three candidates for "Mercado\'s vision" ===\n');
for (const c of candidates) {
  console.log(`[${c.label}]`);
  console.log(`"${c.text}"`);
  console.log(`-> classifyLayer(): ${classifyLayer(c.text)}\n`);
}

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

=== Three candidates for "Mercado's vision" ===

[Real vision]
"The world where anyone discovers, on Mercado, what they didn't know they wanted."
-> classifyLayer(): vision

[Empty slogan]
"Be the best marketplace in the region."
-> classifyLayer(): unclear

[Goal disguised as vision]
"We are going to build the industry's largest catalog, with more than 50 million products."
-> classifyLayer(): unclear

All three candidates "sound" like a vision in casual conversation — all three talk about Mercado's future, all three could show up on a board deck slide. But only the first one passes the test, and for a precise reason: it's the only one that describes a state of the world, with a subject (anyone), an action that subject experiences (discovers), and an observable outcome (what they didn't know they wanted). The other two fail for different reasons, and it's worth naming them separately because they're the two mistakes that show up most often when writing a vision:

• The empty slogan ("be the best") describes no state — it's a superlative with no content. Best at what dimension? Best for whom? What would the world look like if it were true? There's no answer, because the sentence never attempted one. Lesson 6 gives this mistake its full name.
• The goal disguised as vision ("we are going to build... 50 million products") does have specific content and even a number — but it describes an action by the company ("we are going to build"), not a state of the world. It's more honest to call it an objective, or even a catalog strategy, but it isn't a vision: nobody outside Mercado directly experiences "50 million products" as a change in their life. Compare it with the real vision, which does describe something a buyer lives through ("discovers what they didn't know they wanted") without mentioning a single inventory number.

Going deeper: the three-question test

When you're unsure whether a statement is a real vision, ask it these three questions, in order:

1. Does it describe a state of the world, or an action by the company? A real vision can be rephrased as "in this future, [someone] [experiences something]" without ever mentioning the verb "build," "launch," or "invest." If your sentence starts with "we are going to..." it's almost always an objective or a strategy, not a vision.
2. Does it stay true if the strategy changes completely? Mercado could, in five years, radically change strategy — focus on another segment, compete differently — and its vision ("the world where you discover what you didn't know you wanted") would remain intact. If your statement would stop making sense under a different strategy, it isn't a vision: it's strategy with inflated language.
3. Could you, with the same honesty, put a deadline on it? If the natural answer is "by Q3" or "before year end," it isn't a vision — it's a tactic or objective with a date. A real vision makes you a little uncomfortable when you ask it "by when?": the honest answer is "that's not that kind of question."

Common mistakes

Writing a slogan and calling it a vision. What happens: someone writes "be the undisputed leader of the industry" and presents it as the company's vision. Why it happens: it sounds ambitious, fits on one line, and doesn't demand the work of thinking through what specific world is being created. How to spot it: ask classifyLayer, or give yourself the three-question test — if you can't say "leader at what, for whom, doing what specifically," you have a slogan. How to fix it: rewrite it describing the world, not the company's ranking within it. "Be the leader" says nothing about what happens to a user; "the world where X no longer has to Y" does.

Confusing a big objective with a vision. What happens: an ambitious goal with a number attached — "100 million users," "the largest catalog in the region" — gets promoted to vision status. Why it happens: big numbers feel inspiring, and it's easier to measure an objective than to describe a state of the world. How to spot it: apply question 2 of the test — if you change the strategy completely, does the objective still make sense, or does it become arbitrary? "100 million users" only matters if the current strategy points toward scale; under a different strategy (say, a high-margin niche business) that number stops meaning success. How to fix it: separate the two things. The objective can live in the strategy or in a North Star metric (topic of product-metrics-and-experimentation-guide); the vision describes the world, without leaning on any company number.

Writing the vision with investors in mind, not the world that changes. What happens: the vision ends up sounding like a fundraising pitch — "we're going to capture the $X billion market" — instead of a description of the change being sought. Why it happens: the vision often gets drafted in the same meetings where growth and valuation get discussed, and the language rubs off. How to spot it: if your vision mentions market size, valuation, or market share, you're describing the financial result of having succeeded, not the world that success creates. How to fix it: ask "and what does that mean for the person using the product?" until the answer stops mentioning money and starts mentioning a concrete human experience.

Exercises

Exercise 1 — Classify without running the code. For each statement, decide whether classifyLayer would return vision or unclear, and why, before checking:

• (a) "The place where no buyer is left not knowing what exists to solve their problem."
• (b) "Increase buyer retention by 20% this year."
• (c) "Be innovative, approachable, and trustworthy."

See solution

• (a) vision. Contains "the place where" and describes a state of the world (nobody is left not knowing what exists) with no mention of any company action or internal number.
• (b) unclear. It has none of the vision signals in the model ("the world where," "the place where," etc.), and rightly so: it's an objective with a number and a deadline ("this year"), the third clue from the three-question test. It's a legitimate goal, but it isn't a vision.
• (c) unclear. Three adjectives with no subject or object — it doesn't describe who experiences what. It's the empty slogan in its purest form: nothing to rule out, nothing to orient toward.

Exercise 2 — Apply the three-question test. A Mercado colleague proposes this vision: "Be the #1 marketplace by transaction volume in the region by 2030." Use the three questions from "going deeper" to explain, in one paragraph, why this isn't a vision even though it has a date and a number — things that sometimes get mistaken for "seriousness" or "concreteness."

See solution

It fails all three questions in a row. (1) It describes an action/result of the company ("be #1 in volume") — it doesn't describe what happens to a buyer or seller in that world; you could be #1 in volume and change nobody's life. (2) It doesn't survive a strategy change: if Mercado decided to focus on a high-margin niche instead of scale, "be #1 in volume" would stop making sense as an aspiration — that confirms it's an objective tied to this strategy, not a vision above it. (3) It has an explicit deadline ("by 2030"), the clearest signal that it's an objective with a timeline, not a vision — visions don't expire. It's a good business objective; it isn't a vision.

Exercise 3 — Write your own version. Take exercise 2's objective ("be #1 in transaction volume") and rewrite it as a real vision, applying this lesson's definition: describe the state of the world, not Mercado's position in a ranking. (There's no single correct answer.)

See solution

A reasonable version: "The world where buying something new starts with exploring, not searching." Notice what changed: the number disappeared, the date disappeared, and the word "Mercado" disappeared as the sentence's subject — the subject is now the general experience of shopping. If Mercado achieved this, it would probably also be #1 in volume — but volume would be an observable consequence of success, not the definition of success itself. That's the difference between a business objective and a vision: the objective measures success from inside the company; the vision describes success from the life of the person living it.

Summary and next step

A vision describes a future state of the world, not a plan or an objective with a number and a date — it's the render of the finished building, not the construction blueprints. It has a long horizon (10 to 25 years) precisely because it isn't tied to this year's strategy: it can survive several strategy changes without ceasing to be true. With classifyLayer run on three candidates, you saw the two most common impostors: the empty slogan (which describes nothing) and the goal disguised as a vision (which describes a company action or number, not a different world for whoever lives it).

Before moving on you should be able to: state the difference between "state of the world" and "company action" in one sentence; apply the three-question test to any statement someone presents to you as "our vision"; and explain why a big number and a date, far from making a vision more serious, are usually the sign that it's actually an objective.

Lesson 3 takes the vision you just learned to recognize and puts it next to its most commonly confused neighbor: mission. You're going to see that "where we're headed" and "why we exist today" are two different questions, even though they almost always show up together in the same corporate document.

Resources

• Jim Collins, "BHAG (Big Hairy Audacious Goal)" — jimcollins.com/concepts/bhag.html. The 10-to-25-year horizon and the difference between a goal and a real vision, explained by its author. In English.
• Marty Cagan (SVPG), "Vision vs. Strategy" — svpg.com/vision-vs-strategy. Why vision describes the future being created, and strategy describes how you get there — the same render/blueprints distinction from this lesson, in product vocabulary. In English.
• Gibson Biddle, "Intro to Product Strategy" — gibsonbiddle.medium.com/intro-to-product-strategy-60bdf72b17e3. Netflix's former VP of Product on how a product vision connects to the layers that come after it. In English.
• Richard Rumelt, Good Strategy Bad Strategy — goodbadstrategy.com. The origin of the "fluff" vocabulary (inspiring filler with no content) this lesson applies to the vision layer. In English.