product-vision
Product Vision Expert
Overview
The Product Vision is the narrative that sits above the north-star metric. It is the answer to "where are we going and why" -- the story that aligns engineers, designers, marketers, executives, and customers around a single point on the horizon. Without a vision, teams optimize local metrics; with a vision, teams optimize toward a shared destination.
A vision is not a mission statement, not a strategy, not a roadmap. A mission says why the company exists. A strategy says how the company will win. A roadmap says what will ship next quarter. A vision says where the product will be in 5-10 years -- specific enough to inspire engineering decisions today, ambitious enough to outlast any current technology or market condition.
This skill produces the Product Vision document across four canonical formats: Roman Pichler's Product Vision Board (one-page diagnostic), Geoffrey Moore's elevator pitch (single-sentence positioning from Crossing the Chasm), Andy Raskin's strategic narrative (5-act story arc used by Salesforce, Drift, Andreessen-backed companies), and Marty Cagan's 10-year horizon (long-form Cagan-style vision narrative). It also provides a review checklist for testing whether a vision actually works.
When to Use
- New product launch. You are starting a new product and need to articulate the destination before committing engineering quarters.
- Major pivot. The team's direction has shifted and the old vision no longer fits. Reset.
- Strategy reset. Annual or pre-funding-round refresh of the long-term direction.
- Stakeholder misalignment. Engineering, design, and exec teams are pulling in different directions. A re-articulated vision often surfaces the disagreement.
- Hiring at scale. You need a vision compelling enough that prospective hires can decide whether to join. Vague visions repel strong talent.