CAPM Practice: Demonstrate an understanding of product roadmaps

The product vision is the 'North Star' — it defines why the product exists and what it aims to become. The roadmap operationalizes the vision by showing the planned journey from current state to the vision, with themes and milestones along the way.

**Why not A:** A product vision is not a financial projection. While a product vision may indirectly influence financial planning, its purpose is to articulate the future state of the product and the value it will deliver to users and the organization. Financial projections are separate artifacts typically produced by finance teams or included in a business case, not within the product vision itself.

**Why not B:** A product vision is not a technical architecture diagram. Technical architecture documents describe system components, integrations, and infrastructure, which are implementation-level details. The product vision operates at a much higher level, describing the aspirational goal and strategic direction for the product without prescribing how it will be technically built.

**Why not C:** A product vision is not a legal statement or contract. It is a strategic, aspirational description of what the product aims to achieve and the value it will deliver. While a product vision may inform contractual discussions, it is not itself a legally binding document. Its purpose is to inspire alignment among stakeholders and guide decision-making throughout the product lifecycle.