> For the complete documentation index, see [llms.txt](https://docs.hivel.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/reviewing-and-adjusting-kpis.md).

# Reviewing and Adjusting KPIs

**Monthly or Quarterly Reviews:**

* Set up a regular cadence, such as monthly or quarterly reviews, to assess how each KPI aligns with the team’s evolving goals.

**Adjust Targets as Needed:**

* If the team consistently meets a KPI target, consider adjusting the threshold to encourage continuous improvement. Conversely, if a KPI is challenging, adjust the baseline or provide additional resources to help the team meet expectations.

**Learning from Outliers:**

* Use Hivel’s insights feature to investigate outliers and spikes in KPI data. Outliers often reveal bottlenecks or issues that, when addressed, lead to significant performance gains.


---

# 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://docs.hivel.ai/welcome-packet/kpi-planning/kpis-in-hivel/reviewing-and-adjusting-kpis.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.