> 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/intro-to-product-management/what-is-a-product-manager.md). # What is a Product Manager? Product Managers (PMs) are often considered the "voice of the customer" within the company, and they must balance various stakeholders' needs while meeting business objectives and solving problems for the user. It is a strategic role at the intersection of business, technology, and user experience. PMs are responsible for guiding the success of a product and leading the cross-functional team that is responsible for improving it. A Product Manager's role is inherently cross-functional, and they must work closely with teams across the organization to align visions, set objectives, and execute product development plans. Such responsibilities involve setting the product's strategy, defining its roadmap, and working with engineering, design, sales, marketing, and support to deliver a well-rounded product. --- # 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/intro-to-product-management/what-is-a-product-manager.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.