Product vision guide
How to set and communicate product direction
A compelling product vision aligns teams and guides decisions. Without one, every priority debate starts from zero and every roadmap review becomes a negotiation about opinion instead of strategy.
What is a product vision?
A product vision is a concise, inspiring description of what the product will become and why it matters. It is not a feature list — it is the north star that guides decisions when trade-offs must be made.
A good vision answers the question every team member asks when priorities conflict: “Which choice gets us closer to what we are trying to become?” Without it, that question has no principled answer.
Vision vs Strategy vs Roadmap
All three must be aligned. A roadmap that does not connect to the vision is just a feature list.
Where are we going?
3–5 year horizon, inspirationalThe north star. Describes what the product will become and why it matters. Changes rarely — only when the market or fundamental purpose shifts.
How will we get there?
What we will focus on and what we will notThe choices that constrain the roadmap. Which customers, which problems, which advantages. A strategy without explicit non-goals is not a strategy.
What will we build and in what order?
Quarterly executionThe concrete plan. A roadmap that does not connect to the vision is just a feature list. Every item should trace back to a strategic bet.
Writing a product vision statement
A reliable formula gives you a structured starting point. Refine it until it sounds human, not templated.
Formula
“For [target user] who [has a specific need], [product name] is a [product category] that [key benefit / differentiator]. Unlike [alternative], our product [unique advantage].”
Example (fictional)
“For career changers who want to break into tech without a CS degree, NewRoleKit is a career learning platform that provides role-specific roadmaps, practical tools, and job-ready resources. Unlike generic coding bootcamps, we help non-technical professionals become PMs, data analysts, UX designers, and QA engineers in months, not years.”
Amazon’s PR-FAQ method
Write a press release for the product as if it already exists. Then write the FAQ that answers the hardest questions about how you will get there. This forces clarity about what you are building and why.
The press release starts from the customer’s point of view — what they read in a news story the day the product launches. If you cannot write that story compellingly, you have not yet found the right product. The FAQ then stress-tests the idea with the questions an investor, a skeptic, or an engineer would ask.
Using the vision to make decisions
When a stakeholder requests a feature that seems off-strategy, ask: “Does this bring us closer to [vision statement]?” If no, it goes on the backlog or is declined. The vision is not just for external communication — it is a decision filter.
This also changes the nature of disagreement. Instead of “I think we should build X,” the debate becomes “Does X serve our stated vision?” — a question with a more objective answer. Teams that have internalized their vision spend less time in priority debates and more time shipping.
The filter question
For every feature request: “Does building this get us measurably closer to our vision?” If yes, score it for priority. If no, either defer it with a reason or decline it with a reason. Both are acceptable outcomes. Silence is not.
The product strategy (one level below vision)
Strategy translates the vision into choices. Four questions every product strategy must answer.
Who is your primary customer?
Be specific — 'everyone' is not a strategy
Trying to serve everyone means optimizing for no one. Identify the one persona whose problem you solve better than anyone else. Build for them first — the broader market follows when you are undeniably great for someone.
What problem are you uniquely positioned to solve?
Your right to win
What do you know, have access to, or can execute better than competitors? A strategy grounded in a real advantage compounds over time. One built on copying the market leader does not.
What will you NOT do?
Explicit non-goals are as important as goals
Saying no is the hardest part of strategy. Every time you add a non-goal to your strategy document, you protect the team from scope creep, stakeholder pressure, and the instinct to chase every opportunity.
How will you win?
Your unfair advantage
Distribution? Data? Brand? Speed? Network effects? Your advantage does not need to be permanent, but it must be real. If you cannot name it, the strategy is not finished.
Next steps
Learn PM fundamentals
Vision and strategy are core PM skills. The product manager track covers discovery, prioritization, stakeholder communication, roadmaps, and more.