A product vision describes the future state your product creates for customers. It is not a mission statement, a tagline, or a list of features. It answers one question: "If we execute perfectly for the next 3-5 years, what does the world look like for our users?"
The Vision Formula
A strong product vision has three elements:
Who you serve. Be specific. "Everyone" is not a target. "Engineering managers at companies with 50-500 employees" is a target.
What changes for them. Describe the outcome, not the product. "Engineering managers ship reliable software on predictable timelines without burning out their teams."
Why it matters. Connect to a larger trend or problem. "Because software delivery speed is the primary competitive advantage for mid-market companies, and current tools optimize for speed at the cost of sustainability."
String these together and you have a vision: "We help engineering managers at mid-market companies ship reliable software on predictable timelines without burning out their teams, because sustainable delivery speed is the real competitive advantage."
The Process
Step 1: Research. Interview 15-20 customers about their ideal future state. Do not ask what features they want. Ask what their workflow would look like if all their current problems disappeared. Use the user persona builder to synthesize these interviews into clear archetypes.
Step 2: Align with business strategy. Your product vision must serve the company strategy. If the company is pursuing enterprise expansion, your vision cannot focus on individual users. Meet with executives to confirm strategic direction.
Step 3: Draft and test. Write 3-5 candidate visions. Test them with your team. A good vision makes people say "yes, that is what we are building toward." A bad one gets blank stares or "that is too vague to be useful."
Step 4: Commit. Pick one and commit for 12-18 months minimum. A vision that changes quarterly is not a vision. It is a reaction.
Vision vs Strategy vs Roadmap
These are different altitudes:
Vision (3-5 years): Where we are going. Stable, aspirational, directional.
Strategy (1-2 years): How we get there. Which customer segments, which markets, which capabilities. The OKR Generator helps translate strategy into measurable objectives.
Roadmap (1-4 quarters): What we build to execute the strategy. Specific themes, features, and timelines. See the roadmap building guide for the execution layer.
Each level cascades from the one above. If your roadmap items do not connect to the strategy, and the strategy does not serve the vision, you have an alignment problem.
Making the Vision Useful
A vision locked in a slide deck is worthless. Make it a daily decision-making tool:
Prioritization filter. When debating features, ask "does this move us toward the vision?" Use RICE scoring for ranking, but use the vision for filtering. Features that do not serve the vision should not even enter the scoring process.
Hiring guide. Share the vision in job postings and interviews. It attracts people who believe in the direction and filters out those who do not.
Stakeholder alignment. When executives push features that contradict the vision, point to it. "That is a valid idea, but it does not serve our vision of X. Here is what we are focused on instead."