> For the complete documentation index, see [llms.txt](https://docs.sealights.io/knowledgebase/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.sealights.io/knowledgebase/guides/quality-improvement/use-cases-by-persona/managers.md).

# Managers

SeaLights' Quality Improvement approaches empower managers to:

* **Prioritize testing and allocate budget effectively:** Direct resources to high-impact areas based on risk and data, ensuring maximum quality improvement per dollar.
* **Track Progress & Measure Impact:** Monitor testing efforts, measure their effectiveness, and identify areas needing further attention.
* **Make Data-Driven Release Decisions:** Base release decisions on objective data, not gut feeling, for informed and risk-averse choices.
* **Improve Transparency & Communication:** Share data and insights openly with stakeholders, building trust and ensuring everyone is aligned on quality goals.

***

## Tutorials

{% content-ref url="/pages/5cMUjLWdrp0k6hU24s7T" %}
[Effective Prioritization & Budget Allocation](/knowledgebase/guides/quality-improvement/use-cases-by-persona/managers/effective-prioritization-and-budget-allocation.md)
{% endcontent-ref %}

{% content-ref url="/pages/3hnfCuTJzhCRfyD2dLJj" %}
[Tracking Progress & Measuring Impact](/knowledgebase/guides/quality-improvement/use-cases-by-persona/managers/tracking-progress-and-measuring-impact.md)
{% endcontent-ref %}

{% content-ref url="/pages/m9D7v73KZFRuCYvNr8hL" %}
[Data-Driven Release Decisions](/knowledgebase/guides/quality-improvement/use-cases-by-persona/managers/data-driven-release-decisions.md)
{% endcontent-ref %}

{% content-ref url="/pages/gha62ZaJP46ZbWNTtSpe" %}
[Transparency & Communication](/knowledgebase/guides/quality-improvement/use-cases-by-persona/managers/transparency-and-communication.md)
{% endcontent-ref %}


---

# 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://docs.sealights.io/knowledgebase/guides/quality-improvement/use-cases-by-persona/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.