Lesson 9: Product Vision

Every lesson so far has operated at the level of a single decision: is this the right audience (Lesson 5)? What's the real job (Lesson 6)? What's our differentiated value (Lesson 7)? Is this specific assumption worth testing before we build (Lesson 8)? These are all, in a sense, tactical questions — they help you make one good decision at a time. This lesson asks a different kind of question, at a different altitude entirely: where is this product trying to go, over the next several years, and why should anyone — engineers, leadership, users — care enough to follow it there?

A product vision is a clear, compelling description of the future state a product is working toward — typically a three-to-five-year horizon — independent of the specific features or roadmap items that will get it there. It answers "why does this product exist, and what would the world look like if it fully succeeded?" rather than "what are we building next quarter?" A vision is deliberately more stable and more aspirational than a roadmap: roadmaps change constantly as discovery (Lesson 8) reveals new information, but a good vision should remain largely intact across many roadmap iterations, because it operates one level of abstraction above any single tactical decision.

This lesson matters because a team without an articulated vision tends to drift: every quarter's roadmap gets decided in relative isolation, prioritization arguments have no stable reference point above the immediate metric in front of everyone, and the product can end up as a collection of individually reasonable features that don't add up to anything coherent — a symptom closely related to the "trying to be everything to everyone" failure from Lesson 7, but operating at a longer time horizon. A strong vision, by contrast, gives every subsequent roadmap decision a directional test: does this move us toward the future we said we were building, or is it merely locally convenient?

Learning Objectives

1
Define product vision and distinguish it from a mission statement, a value proposition, a strategy, and a roadmap.
2
Explain why a vision should be stable across time while a roadmap changes frequently, and identify the risks of confusing the two.
3
Apply a basic test for evaluating whether a written vision statement is genuinely useful (specific, falsifiable-in-direction, motivating) versus decorative.
4
Identify the "vision without strategy" failure pattern and explain why an inspiring vision alone does not constitute a plan.
5
Use a vision as a filter for evaluating whether a proposed roadmap item is aligned with, neutral to, or in tension with the product's long-term direction.

Lesson 7 (Value Proposition) and Lesson 8 (Product Discovery). This lesson assumes you can write a specific, falsifiable value proposition and understand that discovery is what reveals whether a given path toward a vision is actually working — vision sets the direction; discovery tells you, iteratively, whether you're actually making progress along it.

The Core Definition and Its Neighbors

A product vision describes the future state a product is working toward, typically expressed as a durable narrative rather than a specific list of features: what changes in the world, or in a user's life, if this product fully succeeds? It is useful to precisely distinguish vision from four closely related, frequently confused concepts:

Mission statement: a company-level statement of purpose ("why we exist"), often broader than any single product and more stable even than a vision.
Value proposition (Lesson 7): a specific, comparative claim about why a named audience should choose this product over a named alternative, right now.
Product strategy (Lesson 10): the specific, sequenced set of choices — which markets, which capabilities, in what order — that connects the current state of the product to the vision.
Roadmap: the concrete, time-bound list of initiatives currently planned or in progress, which should serve the strategy, which should serve the vision.

Each layer should exist in service of the layer above it. A common and costly failure is treating these layers as interchangeable — writing a "vision" that is really just a longer list of near-term features, or worse, having no vision at all and mistaking the current roadmap for the product's actual direction.

Why Vision Must Be Stable While Roadmap Changes Constantly

A vision operates at a level of abstraction meant to survive contact with new information from discovery (Lesson 8). If a single failed experiment or a single quarter's disappointing metric requires rewriting the vision itself, the vision was almost certainly written at the wrong altitude — too close to a specific tactical bet, rather than describing a genuinely durable future state.

This distinction has direct practical consequences. A team that conflates vision and roadmap tends to treat any roadmap change as an existential crisis of direction ("we're pivoting again!"), when in fact healthy products change roadmaps constantly and should, because discovery is supposed to keep revealing new information that reshapes near-term plans. What should not change nearly as often is the underlying answer to "what future are we building toward, and why does that matter?" A vision that survives many roadmap iterations, largely unchanged, is doing its job; a vision that needs rewriting every quarter was never really a vision.

What Makes a Vision Statement Actually Useful

A written vision statement can range from genuinely useful to purely decorative, and the difference comes down to three tests:

Specific: does it describe a particular future state, or could it apply equally to any product in any category? ("We will fundamentally change how people manage money" is specific to a domain; "We will make the world a better place" is not.)
Directionally falsifiable: is it possible, in principle, to look at the current state of the world and say whether the company is moving toward or away from this vision? A vision that can never be judged as "off track" gives no real signal about anything.
Motivating: does it give people — particularly engineers and designers doing detailed, often unglamorous work — a genuine reason to care about the outcome, beyond the immediate task in front of them?

A vision statement that fails the specificity test tends to converge on generic, interchangeable language ("empowering people," "delighting customers," "changing the world") that could be printed on the wall of almost any company in almost any industry, and that provides no actual filter for any subsequent decision — echoing the "for everyone" failure from Lesson 7, but at the level of long-term direction rather than audience.

Vision Without Strategy Is Not a Plan

A frequently underappreciated failure mode is the inspiring-but-empty vision: a genuinely well-written, motivating description of a future state, with no accompanying account of the sequenced, concrete choices that would actually get the product there. A vision answers "where are we going and why does it matter"; it deliberately does not answer "how, specifically, do we get there, and in what order" — that is the job of strategy (Lesson 10).

A team can have an excellent, well-communicated vision and still fail completely, if it never translates that vision into a coherent strategy — a sequenced set of near-term bets that plausibly compound toward the described future. Vision without strategy tends to produce two symptoms: either paralysis (everyone agrees on the destination but no one can agree on, or even articulate, a first move), or scattered, uncoordinated activity (many individually plausible initiatives launched in the vision's name, none of them sequenced in a way that actually builds toward it, echoing the same drift problem this lesson opened with, just camouflaged by the presence of an inspiring-sounding vision statement).

Using Vision as a Roadmap Filter

Beyond its motivational role, a vision's most concrete practical use is as a filter for evaluating proposed roadmap items — similar in spirit to the Value Proposition Filter from Lesson 7, but operating at a longer time horizon. Given any proposed initiative, a PM can ask:

Does this initiative move the product meaningfully closer to the described future state?
Is this initiative neutral to the vision — locally useful, but not particularly connected to where the product is ultimately going?
Does this initiative actively pull the product in a direction that conflicts with the vision — solving a real, immediate problem in a way that would make the described future state harder, not easier, to reach?

Notice the third branch does not automatically mean "reject the initiative" — sometimes a genuinely necessary near-term move (a large customer's urgent request, a competitive response) is worth doing even in some tension with the long-term vision, exactly as Lesson 5's Stakeholder Ledger argued divergence should be handled with an explicit, deliberate trade-off rather than either automatic acceptance or automatic rejection. What this filter prevents is the far more common failure: making that trade-off silently, without ever noticing that a locally reasonable decision is quietly working against the very future the team claims to be building.

Common Mistakes to Avoid

Writing a vision that is really just an ambitious feature list

"Our vision is to add AI-powered recommendations, a mobile app, and enterprise SSO" describes a set of features, not a future state — it fails the specificity-about-outcome test, describing means rather than the end they're meant to serve.

Writing a vision so generic it could belong to any company

"We will empower people to achieve their goals" could be printed on the wall of a fitness app, a productivity tool, a bank, or a shoe company. This fails the specificity test and provides no real filter for any decision.

Treating every roadmap change as a sign the vision has failed

Roadmaps should change frequently as discovery reveals new information; conflating this healthy, expected iteration with a failure of vision produces unnecessary anxiety and can pressure teams to stick rigidly to a plan that discovery has already shown to be wrong, purely to preserve an illusion of unwavering direction.

Assuming a well-communicated, inspiring vision is itself a strategy

As covered above, a vision describes a destination; it says nothing about the sequenced path to get there. Teams that stop at an inspiring vision statement, without doing the harder work of Lesson 10's strategic sequencing, often experience either paralysis or scattered, uncoordinated activity.

Never revisiting the vision at all, even when the market fundamentally changes

While a vision should be more stable than a roadmap, "stable" does not mean "permanent regardless of evidence." A genuinely disruptive market shift, a fundamental new discovery about the underlying job (Lesson 6), or a repeatedly failed strategy despite good execution can be legitimate signals that the vision itself, not just the roadmap, needs to be reconsidered — treating vision as entirely beyond question can be just as damaging as changing it too casually.

Product Vision