Product Vision
AI-assisted summary
Product vision serves as a persuasive tool and north star for product teams, articulating the desired future state a product aims to create. An effective vision must be compelling, inspiring, and empowering while being memorable and concrete enough to guide decision-making. Great visions like Google's "organize the world's information" or Disney's "happiest place on Earth" often feel impossible to reach, which drives continuous innovation.
The vision development process involves researching problem spaces, articulating multiple potential futures, and testing with stakeholders, while distinguishing vision (the future you want) from mission (how you'll get there). Modern examples like Josh Miller's Arc browser pivot demonstrate how vision-driven prioritization can lead to strategic course corrections, with vision statements serving as context for teams much like prompts for AI systems.
Introduction
A product vision articulates the desired future state that a product aims to create. It serves as a north star for product teams, aligning efforts and inspiring action. This note explores what makes an effective product vision and how to craft one.
Core Characteristics of Effective Product Visions
Who owns it
- the CEO does not need to be the creator of that vision but must be its keeper (Horowitz)
- story helps you align people behind a shared vision (Fadell)
Persuasive Power
- Admittedly, a good product vision is a bit of an art form, as fundamentally it is a persuasion tool.
- It must convince stakeholders, team members, and users of the value and possibility of a future state
- Effective visions create emotional buy-in, not just intellectual agreement
Emotional Impact
- "When done well, the product vision is compelling, inspiring, and empowering—leaving the product teams feeling excited to begin the hard work of making this vision a reality."
- It should leave product teams feeling excited to begin the hard work of making the vision a reality
- Creates a shared sense of purpose and meaning
Memorable and Concrete
- A good vision is thought-provoking, inspiring, memorable and concrete
- Simple enough to be remembered and repeated
- Specific enough to guide decision-making
- the why behind the product should be crisp & easy to articulate to be able to easily explain why people need it and that's the only way to decide what features it should have (Fadell)
Notable Examples
Google's Early Vision
- Google was using this vision statement when it was kickstarting their activities: "Organize the world's information and make it universally accessible and useful."
- Concise yet comprehensive
- Provides clear direction while remaining flexible for implementation
Example of great vision statements (especially because they are impossible to reach)
- Google: Organizing all the world's information
- Amazon: To be the Earth's most customer centric company
- Apple (not stated explicitly like this): Personal computing can have transformative effects on lives of individuals
- Disneyland: The happiest place on Earth
Restructuring Priorities Example
Manifestos as Visions
- Manifestos are good examples of persuasive visions
- They articulate core principles and desired outcomes
- Examples include the Agile Manifesto, which transformed software development
Creating an Effective Product Vision
Key Components
- Problem Statement: What challenge are you addressing?
- User Focus: Who benefits from your solution?
- Value Proposition: What unique value do you provide?
- Future State: What does the world look like when you succeed?
- Differentiation: How is this different from what exists today?
Vision Development Process
- Research the problem space and user needs
- Articulate multiple potential futures
- Test vision statements with stakeholders
- Refine based on feedback
- Communicate consistently and with conviction
- for a disruptive product you need these 3 things in this order: vision (what you want to make, why, who is it for, why would they pay), insights (from customer and/or market research), data (the scope of opportunity and how people currently use what they use) (Fadell)
- when working on a new version - this order gets reversed to 3-2-1 (Fadell)
- once you have your vision - a good technique to try out is to write a press release for what you want to put out there - it makes you prioritize and focus on what matters (Fadell)
Vision vs. Mission
- Vision describes the future you want to create
- Mission describes how you'll get there
- Both are needed but serve different purposes
Modern Context
- Vision statement is like a context when prompting LLMs
- Great vision statements gives better clarity to teams
Applications
Using Vision to Guide Product Strategy
- Evaluate feature ideas against the vision
- Prioritize initiatives that directly advance the vision
- Make tradeoffs based on vision alignment
Communicating Vision to Different Audiences
- For executives: Focus on business impact and differentiation
- For developers: Emphasize technical challenges and innovation
- For users: Highlight benefits and experience improvements
Vision Validation
- Test vision with users and stakeholders
- Look for emotional resonance and understanding
- Refine the articulation if it's not landing as intended