> 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/process-skills/optimization.md).

# Optimization

Optimization in product management refers to the continuous process of making changes and improvements to a product after its initial launch to enhance its performance, usability, and value to users. This involves analyzing user behavior and feedback, identifying areas of the product that can be improved, and implementing changes based on this analysis. The goal of optimization is to increase user satisfaction, engagement, and retention, and to ensure that the product continues to meet user needs and business objectives effectively. Optimization can involve a wide range of activities, from minor tweaks to user interface elements, to major feature additions or changes, to adjustments in the product's marketing and positioning. It's an ongoing process that requires a deep understanding of the product's users, a data-driven approach to decision making, and a willingness to experiment and learn.


---

# 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.pmguidebook.com/process-skills/optimization.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.
