> 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/overview.md).

# Overview

## Introduction to Product Management

This section provides an in-depth understanding of product management as a discipline. It's the foundation for the rest of the guide, and it's crucial for shaping your approach to the role and helping you navigate the complexities of being a Product Manager.

In this section, we'll explore two aspects of being a PM:

1. [**What is a Product Manager**](/intro-to-product-management/what-is-a-product-manager.md): This topic provides a comprehensive overview of what it means to be a Product Manager and the various aspects of the role. It dives into the roles and responsibilities of a Product Manager, the mindset required for the role, understanding the product management lifecycle, and the different types of Product Managers.
2. [**Product Team Structures**](/intro-to-product-management/product-team-structures.md): This topic explores the common team structures in product management, including stakeholders, leadership, and the company, as well as cross-functional product teams. It provides insights into how product teams are typically structured and the different roles and responsibilities within these teams.


---

# 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/overview.md?ask=<question>&goal=<endgoal>
```

`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.