/product-vision

name: product-vision
description: Help users define a compelling, qualitative description of a future state that aligns decentralized teams and motivates long-term innovation.

Product Vision Creation

Design an aspirational future state that inspires teams and guides strategic decision-making.

Help the user with product vision creation using insights from 22 guests and posts across Lenny's Podcast and Newsletter.

How to Help

1. **Define the Destination** - Guide the user in articulating a lofty yet realistic future state grounded in a potent user problem. 2. **Craft the Narrative** - Help translate technical goals into an emotional metaphor or a strategic narrative that resonates with human psychology. 3. **Visualize the Outcome** - Advise on creating visual prototypes or storyboards that make the abstract vision concrete for stakeholders. 4. **Connect to Execution** - Facilitate the process of working backward from the ideal future to create a tactical multi-year roadmap.

Core Principles

Use Emotional Metaphors

Ami Vora: "If we all agree that the feeling of something should be, I'm sitting in Dolores Park with my friends on a sunny Saturday, then people will just naturally build something that feels more consistent."

Establish a shared emotional metaphor to guide decentralized teams toward consistent decision making without constant oversight.

Ground Vision in Potent Problems

Ebi Atawodi: "So four things. So it has to be lofty, it has to be realistic, it has to be devoid of any tech or limitations of today, and it has to be grounded in a very clear and potent problem. User problem."

Ensure the vision is rooted in a clear and significant user problem that the team feels personally motivated to solve.

Synthesize Across Functions

Mihika Kapoor: "You want to always ensure that there are research insights that help you feel what a user is feeling. You want to ensure that there are beautiful designs and prototypes that help communicate what this future world looks like, and you also want to root it in engineering and feasibility. And you want to be constantly, even in the vision phase, assuring that what you're marching after is something that is achievable and something that you can work towards."

A compelling vision must be a cross-functional blend of deep user empathy, technical feasibility, and visual storytelling.

Balance Art with Science

Sanchan Saxena: "If you become too scientific, you miss out on opportunities because you can't see those opportunities using the scientific method of discovery, because they're too tiny or they're so farfetched that people cannot even understand them."

Avoid over-reliance on scientific methods and A/B testing to prevent missing out on far-fetched or nascent product opportunities.

Unify with a Strategic Narrative

Andy Raskin: "The one thing I say is it's this one story that the CEO uses to drive success in marketing, sales, but also product. That it becomes like a north star, strategic north star for product roadmap, for fundraising, for recruiting, really everything."

Develop a single high-level story that acts as a North Star to align every department from sales to engineering.

Default to Large-Scale Thinking

Shreyas Doshi: "Google, I think the main thing I learned was the power of thinking really big. And I know it sounds like a platitude, but really big. And I only actually realized that when I left Google and I started working with the other teams and these were all capable teams and I was struck by how many teams just limited the potential of what they could achieve."

High-performing cultures prevent teams from setting artificial limits by making large-scale thinking a default operating habit.

Templates & Frameworks

• **Column A vs. Column B Thinking** (Melanie Perkins) - A mental model for strategic planning. Column A is looking at the resources (bricks) you have today and seeing what you can build. Column B is imagining the per
• **The 10-Star Experience Framework** (First-principles thinking) - Brian Chesky's thought experiment for designing extraordinary customer experiences by imagining progressively more extreme versions and then reverse-engineering
• **Three-Year Painted Picture** (How Miro builds product) - A high-level, bold, and ambitious vision document co-developed by the Leadership Team that defines outcomes for users and the company over three years
• **Amazon PRFAQ (Press Release & FAQ)** (Jason Shah) - A document written before building a product to clarify the vision, customer value, and rollout plan.
• **Airbnb Snow White Storyboard Project** (What Seven Years at Airbnb Taught Me About Building a Business) - How Airbnb used Disney-inspired storyboards to map the ideal guest and host experience, identifying key emotional moments and strategic gaps.
• **WhatsApp 'Face-to-Face' Metaphor** (Ami Vora) - An example of using an emotional metaphor to drive decentralized product design decisions.
• **Roman Pichler's Product Vision Board** (My favorite product management templates) - A structured canvas for articulating product vision including target group, needs, product, and business goals
• **Concept Car Prototyping for Long-term Strategy** (Strategy Blocks: An operator’s guide to product strategy) - An approach to generating exploratory prototypes for long-term strategy that are not intended to be production-ready but spark inspiration and identify winning

See `references/artifacts.md` for the full list with details.

Questions to Help Users

• "What specific feeling do you want users to experience when they interact with your product?"
• "If all technical and operational constraints were removed, what would a 15-out-of-10 experience look like?"
• "What is the potent user problem that makes this vision necessary right now?"
• "What does the world look like after your mission is successful in ten years?"
• "Can you describe your product's destination using a non-technica