# Hivel Quadrant With Hivel Quadrant, you get an instant overview of team or user performance in relation to the entire organization. It uses three key metrics—Cycle Time (Speed), Hotfix PRs (Quality), and Deployment Frequency (Throughput)—to visualize where each team or user stands. {% embed url="" %} ### Metrics used in Quadrant 1. **Cycle Time (Speed)**: Measures how quickly work items move from start to completion. 2. **Hotfix PRs (Quality)**: Tracks the number of hotfix pull requests, indicating the quality of code and the need for urgent fixes. 3. **Deployment Frequency (Throughput)**: Measures how often code is deployed to production, reflecting the team's or user's overall productivity and efficiency. ### Quadrant Regions #### 1. Needs Improvement Teams or users in this region are below the org average in both selected metrics. This indicates an opportunity for growth and improvement in both areas. * **Example**: A team with high cycle times and frequent hotfix PRs falls into this category. #### 2. Improve (Any of Speed/Hotfix PRs/Deployment Frequency) Teams or users in these regions need improvement in only one of the metrics, where they lag behind the org average. * **Example**: A team might be shipping faster (less Cycle Time) but have many hotfix PRs, indicating a need to improve code quality. #### 3. Ideal State Teams or users in this region excel in both metrics compared to the org average. They represent high performance in speed and quality, serving as benchmarks for others. * **Example**: A user with a low cycle time, few hotfix PRs, and high deployment frequency exemplifies this ideal state. --- # Agent Instructions: 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: ``` GET https://docs.hivel.ai/using-hivel/hivel-quadrant.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.