defining-product-vision

Guidance for helping someone craft a compelling product vision, drawing on frameworks attributed to 101 product leaders who have defined visions at companies ranging from Notion to Airbnb to the New York Times. It is meant for writing a vision statement, setting long-term product direction, aligning teams on a future state, or distinguishing vision from strategy and roadmap.

The recommended approach is to first clarify scope — separating a vision (long-term aspiration) from strategy (how to win) and a roadmap (what to build) — then focus on describing the user's world five to ten years out rather than product features, push back on vague taglines that do not change behavior, and encourage visual artifacts such as prototypes over abstract documents.

The core principles are illustrated with direct quotes: a vision is not a tagline (Melissa Perri's 'backbone of healthcare' example that no one could elaborate); four criteria that it be lofty, realistic, devoid of today's tech limitations, and grounded in a potent problem (Ebi Atawodi); hiding a radical vision inside a familiar, high-utility form factor (Ivan Zhao, Notion); describing the user's nirvana state without mentioning the company or product, prefixed with 'In the future...' (Ben Williams); moving from the functional 'what' to the emotional 'why' (Chip Conley's 'belong anywhere'); using visual mock-ups (Cam Adams, Canva); letting an emotional metaphor guide decentralized decisions (Ami Vora); and positioning strategy as the choice-forcing connective tissue between mission/vision and plan (Chandra Janakiraman). The skill supplies probing questions to test a draft vision and a checklist of common mistakes to flag — vague taglines, feature lists, mentioning the product, ignoring current constraints, and visions that drive no behavioral change — with a deeper reference file containing all 143 insights from the 101 guests.