> For the complete documentation index, see [llms.txt](https://www.mlcompendium.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.mlcompendium.com/ai-product/product-vision-and-strategy.md). # Product Vision & Strategy A product needs a direction before a backlog. The page goes from vision to strategy and roadmap, then to how a strategy is built, and ends with how the product is positioned against others. The same notes are in [Growth](/ai-product/growth.md). The chain starts with vision, strategy, and roadmap, and a strategy is usually one of 4 strategy types: cost, differentiation, focus, or quality. [what is?](https://www.youtube.com/watch?v=ebwo_BX_VtU) (youtube) walks the full ladder of mission, vision, strategy, roadmap, and execution from a product strategist's point of view. The talk that connects vision to delivery is "[Product Strategy: The Missing Link](https://www.youtube.com/watch?v=x4H_gluZI10)" by Inspired Author Marty Cagan of SVPG at Lean Product Meetup, on youtube. Once the ladder is clear, the strategy itself has to be built. [Strategy should be aligned with Vision](https://www.hotjar.com/product-strategy/) is a complete guide to what a product strategy is, why it matters, the key elements of top strategies, and how to build one yourself. A strategy then has to say where the product stands in the market. [product positioning strategies](https://www.shopkick.com/partners/blog/3-types-of-product-positioning-strategies-and-how-to-best-leverage-them-fc) names three: comparative, differentiation, and segmentation. ## Deprecated links {% hint style="warning" %} These links and images no longer work. The original wording is kept here. A same-resource copy, when one was checked, is used above. {% endhint %} * Vision, Strategy, Roadmap. This address no longer opens: --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://www.mlcompendium.com/ai-product/product-vision-and-strategy.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.