> 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/understanding-and-selecting-kpis.md). # Understanding and Selecting KPIs **Understanding KPIs**\ \ Key Performance Indicators (KPIs) in Hivel are specific metrics chosen to represent essential aspects of your team’s performance. These indicators provide data-driven insights into areas like speed, quality, and team efficiency. Hivel categorises KPIs into Speed Metrics, Quality Metrics and Throughput Metrics to give teams a balanced view across these dimensions. * Speed Metrics: Cycle Time, Deployment Frequency. * Quality Metrics: Change Failure Rate, Mean Time to Repair (MTTR), Flashy Reviews, and Large PRs Reviewed * Throughput Metrics: Commits, PRs Opened, New Work, Active Days \ **Selecting KPIs** Start by defining what success looks like for your team. Are you looking to decrease development cycle time? Increase code quality? Identifying objectives helps choose KPIs that align with those goals. Prioritize based on impact by choosing a manageable set of KPIs that directly impact your team’s objectives. For example: * If reducing bottlenecks is essential, Cycle Time and Review Time might be top priorities. * To improve stability, focus on Change Failure Rate (CFR) and Mean Time to Repair (MTTR). * To reduce Review Time, focus on Avg. Size of PRs and percentage of PRs over 400 LoC * To improve on code quality, focus on Flashy Reviews and Rework. --- # 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/understanding-and-selecting-kpis.md?ask=&goal= ``` `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.