The Most Underrated Document in Product
Most companies have a product vision. Few have one that anyone can remember without looking it up. Even fewer have one that influences actual decisions in the trenches. Vision documents have become a ritual that everyone agrees is important and few people use, which is the most reliable indicator that the documents themselves are wrong.
A real product vision is a description of the future the team is trying to create, specific enough to influence trade-offs and evocative enough to motivate work over years. It is not a slogan, not a mission statement, and not a list of company values. When done well, it is one of the most leveraged documents a PM can write, because it shapes hundreds of decisions made by people who may never read the document directly. Done poorly, it is decoration on a website.
Vision, Mission, Strategy: Distinguishing the Layers
Before writing a vision, it helps to be precise about what it is and is not. The terminology overlaps in casual use, but the concepts are distinct.
Concept Question It Answers Time Horizon
Mission Why does this organisation exist? Indefinite. Often unchanged for
decades.
Vision What future are we trying to bring about? Five to ten years. Anchored in a
specific imagined world.
Strategy How will we get there, given our resources Two to four years. More concrete
and constraints? than vision.
Roadmap What are we building this quarter and the One to four quarters. Highly tactical.
next?
When the four levels are aligned, work flows coherently from purpose to action. When they are misaligned or one is missing, the team flounders. The vision's specific job is to bridge between the indefinite mission and the concrete strategy. Without it, the mission is too abstract to act on and the strategy lacks long-term direction.
What a Great Vision Contains
Great visions vary in tone and topic but share several structural qualities. If yours is missing two or more, it likely will not endure.
1. A Specific Future State
A great vision describes a world that does not yet exist, in concrete enough terms that a team can imagine it. Not we will be the leader in our category , but any small business owner anywhere in the world can launch and run their entire operation from a single tool, without ever needing an accountant, lawyer, or specialist software . The second statement specifies who, what, and how. The first specifies nothing.
2. A Clear Subject and Beneficiary
Who is this vision for? A real vision names a beneficiary, explicitly or by strong implication. Without that, the vision could be anybody's. Saying everyone is a vision-killing answer; it implies the team has not chosen who to serve, which means they will fail to serve anyone particularly well.
3. A Reason It Matters
A vision that describes a future without explaining why anyone should care fails to motivate. The reason can be utilitarian (this future is more efficient, reduces waste, saves time) or emotional (this future restores agency, dignity, joy) or some mix. But the reason must be present, articulated, and connected to a real human need.
4. A Tension With the Present
If the vision is too close to the present, it does not motivate ambition. If it is too far, it feels like fantasy. The right tension is real and uncomfortable: today the world is like this, with these costs to people we care about, and our work is to change that.
5. Durability Across Years
Visions should outlast individual products, individual leaders, and short-term market changes. Test your vision by asking whether it will still be true and useful in five years if the technology stack changes, competitors enter the market, or the team grows tenfold. If a market shift would require rewriting the vision, the vision was at the wrong level.
How to Write One
Vision documents are usually born from a few weeks of intense thinking, refined over months as the team and stakeholders test and react to it. There is no one correct method, but the process we have used most often goes like this.
Step One: Define the Beneficiary in Detail
Before talking about the future, describe the person whose life you are trying to change. Their goals, their constraints, what they currently struggle with, what they would notice if your future arrived. The more concretely you can see this person, the more specific your vision becomes.
Step Two: Describe the World as It Is for Them
Write a paragraph or two describing how the beneficiary experiences the relevant problem today. Specifics over generalities. Frustrations, workarounds, costs, lost time. This becomes the contrast against which your future is meaningful.
Step Three: Describe the World as You Want It to Be
Now write the alternative. What does the beneficiary's life look like when your work has succeeded? Make it specific. They wake up, they do certain things, certain things have become easy that were hard before, certain things have become possible that were impossible. The narrative form helps; bullet points usually do not.
Step Four: Distill the Core
From your detailed description, extract the one or two sentences that capture the essence. This is your vision statement. It should be specific enough to disqualify some directions and evocative enough to remain memorable. Most teams produce too abstract a statement on the first pass; iterate to ground it.
Step Five: Test It Against Decisions
Take three real decisions the team is facing. Apply the vision as a lens. Does it help discriminate between options? If yes, the vision is doing its job. If no, the vision is too vague to be useful. Sharpen until the test passes.
Communicating the Vision
Writing the vision is half the work. Communicating it so that it shapes distributed decisions is the other half. The communication rarely succeeds the first time. It must be repeated, refined, and shown in many contexts before it lives in the team's heads.
Repeat It Until You Are Tired of It
By the time you, the PM, are bored of your own vision, the team is starting to remember it. By the time you cannot stand to say it again, they are starting to use it. The repetition is not redundancy; it is reinforcement against the noise of daily work.
Tell Stories That Embody It
Abstract vision statements live next to concrete stories that illustrate them. The story of one user whose life would change in the way the vision describes is more memorable than any amount of strategic prose. Senior PMs accumulate a library of such stories and tell them often.
Tie Decisions to It Visibly
When making a hard call, explicitly name how the vision shaped the choice. We chose option B because option A would have moved us further from the future where any small business owner can run their operation themselves. This trains the team to use the vision as a tool, not just remember it as words.
Bring It Into Reviews
When reviewing roadmaps and major projects, ask: how does this advance our vision? Things that do not connect should either be reframed or de-prioritised. The vision is the lens through which the work is interpreted; without that lens, it is just decoration.
Common Failures
Failure One: The Slogan Vision
Empowering people. Connecting the world. Reimagining everything. These sound nice and say almost nothing. Any company in any industry could adopt them. They fail the test of specificity and therefore fail to influence decisions. If a competitor in a completely different sector could plausibly use your vision statement, the statement is too generic.
Failure Two: The Internal Goal Vision
Become the largest player in our category by 2030. Reach a billion users. Achieve dominance in the enterprise market. These describe what success looks like for the company, not what the world looks like for users. They motivate executives but not the team in the trenches, because they speak to corporate outcomes rather than human ones.
Failure Three: The Feature List Vision
Build the most comprehensive platform with integrated AI, machine learning, and analytics for every business need. This is a description of features, not of a future. It also commits the team to specific technologies that may or may not still be the right answer in five years. The vision should describe outcomes, not implementations.
Failure Four: The Ageless Mission Disguised as Vision
Make work better for everyone. This may be a fine mission. As a vision, it is too abstract and too perpetual to guide near-future decisions. Visions need a temporal horizon and a specific shape; missions can be eternal.
Failure Five: The Multi-Page Vision
Long, ornate, multi-section documents that try to be vision, strategy, values, and operating principles in one. Nobody reads them. Nobody quotes them. They sit in shared drives. Resist the temptation to merge layers. Write a one-page vision and link out to the strategy and values documents.
Anatomy of Visions That Work
Without naming specific companies (because their language is frequently misquoted and misapplied), here are the structural patterns that recur across vision statements that have endured and shaped real product organisations.
The "Imagine If" Pattern
Many durable visions take the form: Imagine if [specific beneficiary] could [specific capability], so that [specific outcome]. The structure forces specificity at three levels and builds in the contrast with the present (because today they cannot).
The "Eliminate the Need For" Pattern
Many product visions describe what the world would not need anymore if the product succeeded. This is powerful because it frames the product as removing friction rather than adding another tool. Eliminate the need for small business owners to manage their accounting separately from their operations.
The "Default Path" Pattern
Some visions describe a future in which the product's approach becomes the default way of doing something, replacing existing norms. Make code review as natural a part of writing software as compiling it. Visions of this kind are often deeply ambitious; they imply changing not just a market but a culture.
The "Compressed Time" Pattern
Some visions are about time itself: making something that currently takes weeks take minutes, or something that takes minutes take seconds. The compression is the change. What currently takes a small team three weeks to research can be done by one person in an afternoon. These visions tend to age well because the underlying human need (do more with less time) is durable.
When and How to Update a Vision
Visions should be stable but not permanent. Updating them too often makes them feel arbitrary; never updating them allows them to drift from reality. The right cadence is roughly every three to five years, or sooner if a major shift makes the existing vision obsolete. Examples of legitimate triggers for update:
- A technological shift that makes the future you described either already real or no longer relevant.
- A strategic pivot to a meaningfully different customer or problem space, where the old vision no longer fits.
- Significant company growth that changes what is possible. The vision a forty-person company can credibly hold may not be the vision a four-thousand-person company can credibly hold.
- Evidence over time that the vision was wrong, in ways that cannot be fixed by tweaking the strategy below it.
When updating, be transparent about why. The team will accept a well-explained update; they will not accept an unexplained one. Treat vision updates as a milestone, not a routine refresh. The rarity is part of what gives the vision its weight.
A Final Word
A great product vision is one of the highest-leverage things a PM ever writes, because it influences decisions for years, made by people in many roles, often without anyone explicitly consulting the document. The leverage is invisible most of the time. You see it in the consistency of small choices across the team and in the durability of the team's direction through leadership changes and market noise.
Most teams under-invest in their vision because the work is hard to measure and the payoff is delayed. Resist that pull. Spend the time. Write the vision down. Test it against real decisions. Communicate it until you cannot stand to say it. Watch over the next year as the team starts to absorb it and small decisions across the organisation begin to align with it. That alignment is the prize. It is worth the work.
Key Takeaways
- A real vision describes a specific future, names the beneficiary, articulates why it matters, and creates productive tension with the present.
- Vision is not mission, not strategy, not slogan. The four layers (mission, vision, strategy, roadmap) are distinct and must be aligned.
- Write it from the beneficiary's life, not from the company's goals. Test it against real decisions before publishing.
- Communicate it through repetition, stories, visible decisions, and reviews. The communication is half the work.
- Update it every three to five years, or when a major shift makes it obsolete. Stability is a feature; constant change destroys its authority.