Product Vision: The Why Behind Your What

WHY IT EXISTS: Without a shared goal, teams optimize for local concerns. Engineering might prioritize technical debt, marketing might ask for a feature for one campaign, and sales might push for a single customer's request. A product vision prevents this chaos by providing a single, unifying purpose that rises above short-term tactics. It ensures everyone is climbing the same mountain, even if they take different paths.

THE MENTAL MODEL: Think of a product vision as the destination on a map. Your product strategy is the route you plan to take, and your roadmap is the turn-by-turn directions for the next part of the journey. The vision (e.g., 'make sustainable homeownership accessible to everyone') doesn't change often. The strategy might pivot (e.g., 'start with first-time buyers'), and the roadmap will change constantly (e.g., 'build a mortgage calculator this quarter'). The vision provides stability in the face of tactical change.

HOW IT WORKS: A product vision is a short, compelling statement, often supported by a longer narrative or a vision board. It's crafted by the product leader in collaboration with key stakeholders. It should be ambitious but not impossible, and focused on the customer's needs and the change you want to bring to their world. Once established, it's communicated relentlessly. In sprint planning, you ask, 'Does this feature move us closer to the vision?' In a design review, 'Does this experience reflect the future we're trying to build?'

WHEN TO USE IT: A vision is essential for any product or service that will exist for more than a few months. It's the foundation for creating a product strategy and roadmap. It's most powerful when a team needs to make autonomous decisions without constant top-down direction; they can use the vision as their guide. It's also critical for inspiring and motivating a team through the inevitable challenges of development.

WHEN NOT TO USE IT: A vision is less useful for short-term, fire-and-forget projects, like a one-off marketing landing page or an internal script with a single, defined function. In these cases, a clear set of requirements is sufficient. Also, a vision that is too generic ('be the best') or disconnected from reality is worse than no vision at all, as it breeds cynicism and gets ignored. It must be specific enough to be directional.

ONE CANONICAL EXAMPLE: Microsoft's early vision was 'A computer on every desk and in every home, running Microsoft software.' This statement was incredibly ambitious in the 1970s. It was not a feature list. It didn't say how they would do it. But it clearly stated the intended future state and provided a powerful filter for every strategic decision the company made for decades, from building operating systems to developing office applications.