Clarifying Product Strategy
A PM's hierarchy of terms often gets jumbled, but getting it right is key to better decision-making. A recent post clarifies the distinction: the roadmap is not the strategy, the strategy is not the vision, and the vision is not the mission. Understanding this cascade unlocks focus and alignment across teams.
A company's mission is its long-term, stable purpose; for Google, it's "to organize the world's information," while Amazon's is to be "earth's most customer-centric company." This overarching "why" anchors all subsequent product decisions and remains constant for years. Flowing from the mission, a product vision statement defines the product's ultimate goal and the change it aims to create for users. For example, Zoom's vision "to make video communication frictionless" guides its development toward simplicity and ease of use, serving as a north star for the entire team. A strong vision inspires and keeps the user at the center of every decision. The product strategy then acts as the bridge from the aspirational vision to tangible action. It's the high-level plan detailing the target audience, the unique value proposition, and the specific business goals the product will achieve. This strategic layer forces teams to make deliberate choices about what to pursue and, just as importantly, what to ignore. A product roadmap operationalizes the strategy, outlining the key initiatives and problems to be solved over a specific timeframe. A common mistake is creating a static list of features with deadlines, which can disappoint stakeholders and limit the ability to adapt. Instead, modern roadmaps are flexible and focus on outcomes over outputs. The absence of this clear, cascading alignment is a statistically significant indicator of low-performing teams. Without a well-communicated corporate strategy to connect to, teams lack direction, motivation plummets, and day-to-day activities become disconnected from larger company goals. To structure this strategic thinking, product managers often use established frameworks. Objectives and Key Results (OKRs) help cascade strategic goals and keep initiatives measurable, while the "Jobs to be Done" framework ensures features are built to solve specific user needs. The North Star framework identifies the single most important metric that captures the value delivered to users. Misalignment between these elements often leads to a "feature factory" mindset, where the focus is on shipping functionality rather than creating value. This happens when stakeholder requests that aren't aligned with the core strategy are prioritized, resulting in a product that is a collection of unrelated features with a weak value proposition.
