A long-term aspirational statement of the future state
A vision is the long-term future state a product is working toward, stated vividly enough that a team can tell whether a given decisionDecisionStrategyA recorded decision with context, rationale, and consequencesView reference → moves closer to it. It sits years out and changes rarely, which is precisely why it is so often faked. Most documents labelled "product vision" are slogans about purpose, and the gap between a slogan and a described future is where the concept earns its definition.
The case for starting from a fixed why was popularised by Simon Sinek in *Start With Why* (2009), built on his Golden Circle of Why, How, and What. Sinek's claim is that durable organisations communicate from the inside out, leading with the belief that motivates the work before the work itself. The why is timeless and emotional; it is the purpose that outlasts any particular product.
Product practice sharpened this into a specific artefact and drew a line Sinek's model leaves blurry. Marty Cagan argues that most teams confuse a product vision with a mission statement, mistaking a slogan about purpose for a described future. In his account a product vision is the future you are trying to create, typically two to five years out, concrete enough that people can picture the experience. Roman Pichler frames the vision as the ultimate reason for creating the product, the positive change it should bring about.
The settled distinction separates three layers that often collapse into one. The vision is the destination. The missionMissionStrategyThe purpose and reason the product existsView reference → is what the organisation does day to day to pursue it. The strategy is the chosen path: the bets, the audiences, the sequencing that turn the vision into reachable steps. Cagan likens vision and strategy to leadership and management, where the vision inspires and sets direction and the strategy gets you there.
A documentation tool writes its vision as a scene set in 2029: "any team can ask a question in plain language and get an answer assembled from their own product knowledge, with no one maintaining a wiki." It is testable as a future, not as a metricMetricStrategyA unified metric that measures progress, health, or behaviour across the productView reference →. Anyone can ask whether a proposed featureFeatureProduct SpecificationA product capability or featureView reference → moves toward that scene.
The vision then disciplines lower layers. The mission, "make a team's product knowledge structured and queryable", is what the company does now. The strategy picks the path: start with engineering teams who already write structured docs, win on capture speed before breadth. When a large customer requests a heavy permissions system, the team weighs it against the vision and finds it orthogonal, so it goes to Later on the roadmapRoadmapProduct SpecificationA strategic plan of features and milestonesView reference → and capture work keeps its place. The vision did not decide the feature; it decided the feature was not yet on the critical path.
In the Unified Product Graph, a vision is the root of the Strategy & OutcomesOutcomeStrategyA desired business or user outcomeView reference → region, whose shape is a cascade from aspiration down to proof. It descends through vision_realised_through_missionvision_guides_objective
Type-specific fields on BaseNode
timeframestringTarget timeframe. @example "3 years"
north_starstringSingle north-star metric or statement
success_looks_likestringNarrative of what success looks like
idstringrequiredUnique identifier (UUID)
typeNodeTyperequiredDiscriminator for the entity type
titlestringrequiredDisplay name
descriptionstringOptional detailed description
statusstringLifecycle status
tagsstring[]Freeform tags for filtering
4 phases — initial: drafting
5 edge types connected to this entity.
product_guided_by_visionvision_realised_through_missionvision_guides_objectivedocument_describes_visionvision_guides_strategic_theme