> 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-managers.md).

# Product / Program Managers

Someone has to own the product and the program. The page points first at the product side, the AI product manager, and then at the program side, the data program manager.

The same notes are in [Project Management](/ai-product/management.md#project-management).

The product owner comes first, because an AI product fails differently from ordinary software. [the AI PM](https://emerj.com/ai-executive-guides/ai-product-manager/) is written for someone who finds themselves in the role of an AI product manager, and covers what it takes to deliver a successful AI product at a company, a role the guide calls key for the future of AI deployment.

Once the product has an owner, the data work around it still needs someone to run the program. [The Data Program Manager](http://www.ddmcd.com/dpm-intro) is an introduction to Data Program Management (DPM) from [www.ddmcd.com](http://www.ddmcd.com).


---

# 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-managers.md?ask=<question>&goal=<user_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.
