Principles of Product Management: Product Vision (Vision Statement, Product Vision Board, Elevator Pitch)

Product Vision (Vision Statement, Product Vision Board, Elevator Pitch)

Product Vision: The North Star for Building What Matters

A product vision is a concise, inspiring declaration of why your product exists and the long-term impact it aims to create. It’s not a roadmap or a feature list—it’s the "why" that guides every decision, aligns teams, and keeps stakeholders focused on the bigger picture. Without a clear vision, products drift into feature factories or local maxima (e.g., optimizing for short-term metrics at the cost of long-term value).

Real-world example: Slack’s original vision wasn’t "a chat app" but "to make work simpler, more pleasant, and more productive"—a guiding light that shaped everything from their onboarding (minimal friction) to integrations (reducing context-switching). Compare this to competitors who built "yet another enterprise chat tool" and failed to differentiate.

Key Terms & Frameworks

• Product Vision Statement:
  A 1–2 sentence aspirational declaration of your product’s purpose and impact. Template: "For [target user], [product name] is a [category] that [key benefit]. Unlike [alternative], we [differentiator]."

• Example (Tesla): "To accelerate the world’s transition to sustainable energy."

• Product Vision Board (Roman Pichler):
  A one-page visual framework with 4 components:

• Vision (the "why")
• Target Group (who it’s for)
• Needs (user problems/jobs to be done)
• Product (high-level solution)

• Example: For a mental health app, the board might show: Vision = "Reduce stigma around therapy," Target Group = "Gen Z professionals," Needs = "Quick, affordable access to therapists," Product = "AI-matched therapy sessions via chat/video."

• Elevator Pitch:
  A 30-second persuasive summary of your product’s value, structured as: "[Problem] affects [target user]. Today, they use [alternative], which [limitation]. Our product, [name], solves this by [key benefit]. Unlike [competitor], we [differentiator]."

• Example (Notion): "Teams struggle to organize knowledge across tools like Google Docs and Trello, which are siloed and hard to search. Notion solves this by combining docs, wikis, and databases in one flexible workspace. Unlike Confluence, we’re intuitive for non-technical users."

• Jobs to Be Done (JTBD):
  A framework to define the "job" users "hire" your product to do. Formula: "When [situation], I want to [motivation] so I can [outcome]."

• Example (Instagram): "When I see a beautiful moment, I want to share it instantly so I can feel connected to friends."

• North Star Metric (NSM):
  The single metric that best captures the core value your product delivers. Example: For Airbnb, it’s "nights booked" (not revenue or DAU), because it directly reflects their mission of "belonging anywhere."

• Vision vs. Strategy vs. Roadmap:

• Vision: Why we exist (e.g., "Democratize access to financial tools").
• Strategy: How we’ll win (e.g., "Partner with neobanks to offer embedded finance").

• Roadmap: What we’ll build (e.g., "Launch savings feature Q3").

• Moonshot vs. Roofshot:

• Moonshot: Ambitious, long-term vision (e.g., "Self-driving cars for all").

• Roofshot: Near-term, incremental goals (e.g., "Improve lane-keeping accuracy by 20% this year").

• OKRs (Objectives and Key Results):
  A goal-setting framework to align vision with execution. Formula:

• Objective: Qualitative, inspiring goal (e.g., "Become the default payment app for Gen Z").

• Key Results: 2–4 measurable outcomes (e.g., "Increase Gen Z MAU by 30%," "Reduce checkout friction to <2 taps").

• The "5 Whys" Technique:
  A root-cause analysis tool to uncover the real problem behind a symptom. Ask "why?" 5 times to dig deeper.

• Example:

  
  
  1. Why are users churning? → "They’re not finding value."
  2. Why? → "They don’t complete onboarding."
  3. Why? → "It’s too long."
  4. Why? → "We ask for too much info upfront."
  5. Why? → "We designed it for sales, not users."

• The "Even Over" Statement:
  A prioritization tool to clarify trade-offs. Template: "We will prioritize [X] even over [Y]."

• Example (Spotify): "We will prioritize discovery even over playlists." (Explains why they invest in algorithms over user-curated playlists.)

Step-by-Step: How to Craft a Product Vision

1. Start with the "Why" (Vision Statement)

• Action: Write 10+ "why" statements for your product (e.g., "Why does this product exist?"). Use the 5 Whys to dig deeper.
• Example: For a fitness app:
  1. Why? → "To help people get fit."
  2. Why? → "Because fitness improves health."
  3. Why? → "Because health reduces healthcare costs."
  4. Why? → "Because people deserve to live longer, happier lives."
  5. Why? → "Because we believe everyone should have access to tools for a fulfilling life."

• Refine into a vision: "To empower everyone to live healthier, happier lives through accessible fitness."

• Template: Use the "For [user], [product] is a [category] that [benefit]. Unlike [alternative], we [differentiator]." framework.

• Example (Duolingo): "For language learners, Duolingo is a gamified app that makes learning fun and accessible. Unlike Rosetta Stone, we’re free and bite-sized for busy people."

2. Validate with Stakeholders & Users

• Action: Test your vision with:
• Internal teams: Does it inspire engineers, designers, and marketers? If not, it’s too vague.
• Users: Ask 5–10 target users, "Does this resonate with you? Why or why not?"
• Data: Check if your vision aligns with user behavior (e.g., if your vision is "reduce loneliness," but users only use your app for productivity, there’s a mismatch).

3. Build the Product Vision Board

• Action: Fill in the 4 quadrants (Vision, Target Group, Needs, Product) using sticky notes or a template.
• Example (Calm app):
  • Vision: "Make mental wellness a daily habit."
  • Target Group: "Busy professionals aged 25–45."
  • Needs: "Quick stress relief, better sleep, mindfulness on-the-go."
  • Product: "Guided meditations, sleep stories, and breathing exercises in <5-minute sessions."

4. Craft the Elevator Pitch

• Action: Use the elevator pitch template to distill your vision into a 30-second story.
• Example (Zoom): "Remote teams struggle with clunky video calls that drop or lag. Today, they use Skype or Hangouts, which are unreliable and lack features. Zoom solves this by offering crystal-clear video, screen sharing, and recording in one app. Unlike WebEx, we’re easy to use and work on any device."

5. Align with Strategy & OKRs

• Action: Translate your vision into strategy (how you’ll win) and OKRs (measurable goals).
• Example (Vision → Strategy → OKRs):
  • Vision: "Make work simpler for remote teams."
  • Strategy: "Become the default collaboration hub by integrating with all major tools."
  • OKRs:
  • Objective: "Become the #1 remote work tool for startups."
  • Key Results:
    1. "Increase DAU by 40% among startups."
    2. "Integrate with 10+ major tools (Slack, Notion, etc.)."
    3. "Reduce time-to-first-value to <2 minutes."

6. Socialize & Iterate

• Action: Share your vision with:
• Leadership: Get buy-in by tying it to business goals (e.g., "This aligns with our mission to reduce churn").
• Teams: Use it to align roadmaps (e.g., "Does this feature support our vision of ‘simplifying work’?").
• Users: Reference it in marketing (e.g., "Built for [vision]").

Common Mistakes

• Mistake: Confusing vision with features or roadmaps.

• Correction: A vision is why you exist, not what you’ll build. Example: "We’re building a chat app" (❌) vs. "We’re making work communication effortless" (✅).

• Mistake: Making the vision too broad or generic.

• Correction: Avoid clichés like "make the world a better place." Be specific. Example: "Help small businesses accept payments without fees" (✅) vs. "Disrupt payments" (❌).

• Mistake: Ignoring user needs in the vision.

• Correction: Your vision should solve a real problem. Use JTBD or 5 Whys to validate. Example: If users don’t care about "AI-powered," don’t include it in your vision.

• Mistake: Not aligning the vision with business goals.

• Correction: Tie your vision to revenue, retention, or growth. Example: If your vision is "reduce loneliness," but your business model is ads, there’s a misalignment.

• Mistake: Setting a vision that’s too safe or incremental.

• Correction: A vision should be ambitious but achievable. Use moonshot vs. roofshot to balance. Example: "Be the best email app" (❌) vs. "Eliminate email for teams" (✅).

PM Interview / Practical Insights

1. "How do you create a product vision?"

• What they’re testing: Can you articulate a clear, user-centric vision and tie it to execution?
• How to answer:
• Start with the user problem (use JTBD or 5 Whys).
• Define the long-term impact (vision statement).
• Validate with data/stakeholders.
• Align with strategy and OKRs.
• Example: "For a food delivery app, I’d start by asking why users order food. If the answer is ‘convenience,’ the vision might be ‘Make food delivery so fast and reliable that cooking at home feels like a chore.’ I’d validate this with user interviews and data on order frequency, then align it with OKRs like ‘Reduce delivery time by 20%.’"

2. "How do you handle a stakeholder who wants to change the vision?"

• What they’re testing: Can you balance flexibility with conviction?
• How to answer:
• Listen: Understand their concerns (e.g., "This doesn’t align with our revenue goals").
• Validate: Check if the change is data-driven or opinion-based.
• Compromise: Adjust the vision if it’s a better path, but push back if it’s short-term thinking.
• Example: "I’d ask what problem they’re trying to solve. If it’s a misalignment with business goals, I’d propose a workshop to refine the vision together. If it’s just a preference, I’d share user data to explain why the current vision works."

3. "Vision vs. Strategy vs. Roadmap – what’s the difference?"

• What they’re testing: Do you understand the hierarchy of product planning?
• How to answer:
• Vision: Why we exist (e.g., "Democratize finance").
• Strategy: How we’ll win (e.g., "Partner with banks to offer embedded tools").
• Roadmap: What we’ll build (e.g., "Launch savings feature Q3").
• Trap: Don’t say the vision is "to build X feature"—that’s a roadmap item.

4. "How do you know if your vision is working?"

• What they’re testing: Can you measure long-term success?
• How to answer:
• Leading indicators: User behavior (e.g., retention, NPS, feature adoption).
• Lagging indicators: Business outcomes (e.g., revenue, market share).
• North Star Metric: The one metric that best reflects your vision (e.g., "nights booked" for Airbnb).
• Example: "For a social app, I’d track DAU and retention, but the North Star might be ‘meaningful connections per user.’ If that’s declining, the vision isn’t resonating."

Quick Check Questions

1. Your team wants to add a social feature to a productivity app to increase engagement, but user interviews show it would hurt NPS. How do you decide?

• Answer: Prioritize NPS and long-term vision over short-term engagement.
• Why: A vision like "make work simpler" doesn’t align with social features. Use Even Over Statements (e.g., "We prioritize productivity even over engagement") to guide the decision.

2. A stakeholder says, "Our vision should be ‘to build the best X in the world.’" How do you respond?

• Answer: Push back—this is a feature, not a vision.
• Why: A vision should focus on impact (e.g., "make X accessible to everyone"), not features ("best X"). Use the 5 Whys to dig deeper.

3. Your product’s vision is "to reduce food waste," but your roadmap is full of features for restaurants. What’s wrong?

• Answer: The vision and roadmap are misaligned.
• Why: If the vision is about reducing waste, the roadmap should focus on consumers (e.g., "track expiration dates") or suppliers (e.g., "donate surplus food"), not just restaurants. Use the Product Vision Board to realign.

Last-Minute Cram Sheet

1. Vision statement template: "For [user], [product] is a [category] that [benefit]. Unlike [alternative], we [differentiator]."
2. Product Vision Board: Vision + Target Group + Needs + Product.
3. Elevator pitch: Problem → Alternative → Solution → Differentiator.
4. JTBD formula: "When [situation], I want to [motivation] so I can [outcome]."
5. North Star Metric: The one metric that best reflects your vision (e.g., "nights booked" for Airbnb).
6. Vision vs. Strategy vs. Roadmap: Why → How → What.
7. 5 Whys: Dig deeper to find the root problem.
8. Even Over Statement: "We prioritize [X] even over [Y]." (e.g., "We prioritize privacy even over growth.")
9. ⚠️ Vision ≠ Features: "Build the best chat app" (❌) vs. "Make communication effortless" (✅).
10. Moonshot vs. Roofshot: Long-term ambition vs. near-term goals.