> For the complete documentation index, see [llms.txt](https://www.pmguidebook.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.pmguidebook.com/knowledge-skills/data-driven-decisions.md). # Data-Driven Decisions Data-Driven Decisions in product management refers to the practice of making decisions based on evidence and validated learnings, rather than just intuition or guesswork. Product Managers can leverage data to inform their decisions at each stage of the development process, from ideation to launch. This includes understanding user behavior, measuring product performance, identifying trends, and predicting future outcomes. A data-informed product strategy is based on both qualitative and quantitative data, providing a comprehensive understanding of customer needs, behaviors, and preferences. This data-driven approach helps Product Managers make informed decisions, select features that positively impact the business, and align stakeholders. However, while data is a powerful tool, it's also essential for Product Managers to balance data-driven decisions with other factors such as user feedback, business objectives, and market trends. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://www.pmguidebook.com/knowledge-skills/data-driven-decisions.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.