Mission vs. vision: why we exist today, where we're headed tomorrow

Description

Lesson 2 defined vision: the future state of the world the company seeks to create, with a long horizon (10 to 25 years) and no honest deadline. This lesson introduces its most commonly confused neighbor: mission. If vision answers "where are we headed, and why does it matter?", mission answers a different, more urgent question: "why do we exist, today, exactly as we are right now?". It isn't "what world do we want to create in 20 years?" — it's "what problem do we solve, for whom, today, with what we've already built?"

The confusion between the two is so common that most corporate documents blend them into a single paragraph, and sometimes swap them without anyone noticing. The fastest way to tell them apart: vision can be phrased without ever mentioning the company — it describes the world; mission almost always starts with "we exist to..." or "we help...," with the company as the active subject of the present tense. One is about the destination; the other is about the reason you already set sail.

Connection to the module. In lesson 2 you learned to tell a real vision apart from an empty slogan. Here you take the next necessary step before reaching the full four-layer map (lesson 4): separating vision from the layer it most resembles, and most gets confused with in practice. Without this clear distinction, it's impossible to build next lesson's four-layer map — mission and vision would blend into a single box.

An everyday analogy: the reason for the trip and the star that guides it

Imagine a hospital ship sailing the coast, bringing medical care to communities with no nearby hospital access. If you ask the crew why they set sail this morning, the answer is concrete and present-tense: "we exist to bring free medical care, today, to coastal towns without a hospital less than a day's travel away." That's the mission. It's what gets them out of bed, what justifies today's fuel, what a donor understands immediately without needing any extra data. And, notably, it's something they're already fulfilling, on this very trip, with the ship they have.

Now ask them where, ultimately, all this effort is headed. The answer shifts registers entirely: "a world where no coastal town goes without medical care for being far away." They're not going to achieve that today, not with this ship, and maybe not in the lifetime of whoever says it — that's the vision, the horizon that gives long-term meaning to each individual trip. Notice something important: the mission doesn't change even if they change route, ship, or crew — it's still "medical care today, here" — and the vision doesn't change even if they end up serving ten more towns than planned this year. They're two clocks running at different speeds, and confusing them — using one's language for the other — is this lesson's central mistake.

The exact same thing happens at Mercado. Its mission is "we exist to connect curious buyers with trusted local sellers, today" — something the platform, as it's built right now, already does, every day. Its vision is "the world where anyone discovers, on Mercado, what they didn't know they wanted" — a horizon that orients where the platform grows over the years, without today's mission needing to change for that to remain true.

Worked example: two Mercado statements, classified

Let's go back to classifyLayer, now with Mercado's real vision and mission, side by side, to precisely see what signal the model uses to tell them apart.

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 mercadosMission = 'We exist to connect curious buyers with trusted local sellers, today.';

console.log('=== Vision vs mission: the same company, two different questions ===\n');
console.log('Vision :', '"' + mercadosVision + '"');
console.log('  -> layer:', classifyLayer(mercadosVision));
console.log('');
console.log('Mission :', '"' + mercadosMission + '"');
console.log('  -> layer:', classifyLayer(mercadosMission));

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

=== Vision vs mission: the same company, two different questions ===

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

Mission : "We exist to connect curious buyers with trusted local sellers, today."
  -> layer: mission

classifyLayer tells the two sentences apart with a very simple signal — "the world where" in one, "we exist to" and "today" in the other — but that surface signal reflects a real underlying difference. The vision never mentions Mercado as its subject: it talks about "anyone" and what happens to them. The mission does put Mercado as the active subject ("we exist to connect") and anchors everything in the present ("today"). That's the test you can run yourself, with no model at all: if the sentence describes what happens to someone outside the company, in a future with no date, it's vision. If it describes what the company does, today, and why, it's mission.

Going deeper: the table of two questions

	Vision	Mission
Question it answers	Where are we headed, and why does it matter?	Why do we exist, today?
Horizon	10-25 years, no honest deadline	Right now, with what already exists
Subject of the sentence	The world / the person living it	The company, in the first person
Does it change with strategy?	No -- it survives several strategy changes	Rarely -- it's almost as stable as the vision
Can you "achieve" it and be done?	No -- it's a direction, not a destination you reach	Yes, in the sense that it's lived out by fulfilling it every day
Mercado's example	"The world where you discover what you didn't know you wanted"	"We exist to connect buyers and local sellers, today"

There's a short way to remember it that served the hospital ship's crew well: the mission is what you're already doing well; the vision is why continuing to do it matters more than it seems today. If you ask a new engineer on the team "why do you work on this?", a good answer blends both, without confusing them: "Today, I help a buyer find a trusted local seller [mission] — and in the long run, that builds a world where nobody misses out on knowing something better existed for their problem [vision]."

Common mistakes

Writing the mission with the same horizon as the vision. What happens: the mission ends up written as "be the marketplace that transforms commerce forever" — a 20-year sentence disguised as "why we exist today." Why it happens: it feels more inspiring to write big, and separating "today" from "forever" seems to strip ambition from the text. How to spot it: ask whether the mission would have been just as true five years ago, before the company had half the product it has today. If the answer is no — because it describes capabilities that don't exist yet — it isn't a mission: it's a vision with a present-tense verb. How to fix it: anchor the mission in what the company already does, today, with what it has already built. Leave the full, long horizon for the vision.

Having a vision without a mission (or vice versa). What happens: a company has an inspiring vision painted on the office wall, but nobody can explain in one sentence why it exists today, beyond "to make money." Or the reverse: its daily purpose is crystal clear, but it never asked where that work is ultimately headed over ten years. Why it happens: writing the vision is more fun — it lets you dream; writing the mission demands the humility of precisely describing what's done today, no more, no less. How to spot it: ask someone on the team "why does this company exist, today?" and "where is it ultimately headed?" — if they answer both the same way, or can't answer one of the two, one of the layers is missing. How to fix it: write the two separately, each answering only its own question, and verify with classifyLayer (or this lesson's table) that they haven't blended together.

Using "mission" and "vision" as interchangeable synonyms in conversation. What happens: in a meeting someone says "our mission is to be the world where..." — mixing one layer's vocabulary with the other's content. Why it happens: in everyday corporate English and Spanish, "mission statement" sometimes gets used as an umbrella for "the whole purpose text," without distinguishing the two questions. How to spot it: if "we exist to" and "the world where" show up in the same sentence, two layers probably got mixed into one. How to fix it: require every document to have two separate sentences, each answering only its own question — not a hybrid sentence that tries to answer both at once and ends up answering neither precisely.

Exercises

Exercise 1 — Classify without running the code. For each hospital-ship statement, decide whether classifyLayer would mark it vision or mission, and why:

• (a) "We help coastal communities without medical access receive care today."
• (b) "Someday, no coastal town will go without medical care because of distance."

See solution

• (a) mission. Contains "we help" (one of the mission signals) and describes something the organization does in the present, with its own active subject.
• (b) vision. Contains "someday" (a vision signal) and describes a future state of the world with no mention of the organization as subject — the subject is "no coastal town."

Exercise 2 — Spot the blend. A Mercado coworker proposes this single sentence as "our mission and vision": "We exist to be, someday, the world where every purchase starts with a discovery." Explain why this sentence mixes the two layers, and split it into two correct sentences.

See solution

The sentence mixes "we exist to" (mission signal, present tense, active subject) with "someday" and "the world where" (vision signals, future with no company subject) in the same sentence — it tries to answer both questions at once and so answers neither precisely (in fact, classifyLayer would mark it according to the model's search order, not according to which intent "weighs more" for a human — another reason not to mix them).

Correctly separated:

• Mission: "We exist to help buyers find what they're looking for today, and local sellers get found by them."
• Vision: "The world where every purchase starts with a discovery, not a search."

Exercise 3 — The five-years-ago test. Take Mercado's mission ("we exist to connect curious buyers with trusted local sellers, today") and ask yourself: would it have been just as true five years ago, when the platform had a fraction of today's catalog and users? If the answer is yes, what does that tell you about the difference between a mission and a growth objective?

See solution

Yes, it would have been just as true: five years ago, with a smaller catalog, Mercado was already connecting curious buyers with trusted local sellers — at a smaller scale, but with the same purpose. That confirms it's a real mission, not a growth objective in disguise: a growth objective ("reach X sellers") would indeed have been different five years ago, because it describes a magnitude, not a purpose. The mission doesn't grow or shrink with the size of the company — it describes why it exists, and that's just as true with ten sellers as with ten thousand.

Summary and next step

Vision and mission answer different questions and run at different speeds: vision describes where the world is headed because of the company, with no honest deadline; mission describes why the company exists today, with what it has already built. The quick test you learned: if the sentence's subject is "the company, in the present," it's mission; if the subject is "the world, or whoever lives in it, in a future with no date," it's vision. You saw classifyLayer tell Mercado's two real sentences apart using that same signal.

Before moving on you should be able to: write any organization's mission and vision as two separate sentences, without blending them; and explain, using the five-years-ago test, why a real mission doesn't change with the size of the company.

Lesson 4 completes the map: it takes vision and mission, and adds the two missing layers — strategy and tactics — to show how all four stack up and how each one constrains the one below it.

Resources

• Marty Cagan (SVPG), "Product Vision vs. Mission" — svpg.com/product-vision-vs-mission. The article that names this exact confusion from the product side, with examples of teams that blend them without noticing. In English.
• Marty Cagan (SVPG), "Product Vision FAQ" — svpg.com/product-vision-faq. Real follow-up questions from product teams trying to separate the two layers in practice. In English.
• Jim Collins, "BHAG (Big Hairy Audacious Goal)" — jimcollins.com/concepts/bhag.html. Built to Last distinguishes the "core purpose" (close to mission) from the BHAG (the long-term vision) as two separate pieces of a durable organization's core. In English.
• Gibson Biddle, "Intro to Product Strategy" — gibsonbiddle.medium.com/intro-to-product-strategy-60bdf72b17e3. How a former Netflix VP of Product places vision and purpose before getting into strategy proper. In English.