What this section is for
Choose a metric, set the value you want and select the calculation period. Specify whether improvement means an increase or a decrease. The page shows the current value, target status and trend. You can compare targets with built-in or custom benchmarks.
When to use
- To set a measurable goal, such as reducing the wait for a review.
- When choosing which team metrics to improve first.
- At a regular meeting, to check progress against existing targets.
Quick start
- 1Create a target: pick the metric, set the target value and unit, choose the direction, and set an evaluation window in days.
- 2Compare the target with the team’s current value and a selected benchmark. Check whether the benchmark suits your service.
- 3Agree who will follow up on the target and record the owner outside this section.
- 4Read status alongside the trend. A metric can be getting worse even when its current value meets the target.
Key settings
| Setting | What it does | How to use it | Common mistake |
|---|---|---|---|
| Metric type | Selects which measurement the target is evaluated against. | Choose a metric with connected data. For example, a test-coverage target needs a coverage data source. | Counting changes in correlated metrics as separate improvements. |
| Target value and direction | Defines the number to reach and whether progress means going up or down. | Choose lower is better for time to production and failure rate. The wrong direction reverses the meaning of the status. | Leaving higher is better selected for a metric you want to reduce. |
| Evaluation window | The number of days over which current value is computed (1 to 365). | Choose a period with enough observations. You can start with 30 days and check how much individual events affect the result. | A 7-day window on a slow metric, which produces a status that flips every review. |
Usage example
Scenario: The team wants to reduce the wait for a review.
- 1Create a target on review turnaround with a value in hours, direction set to lower is better, and a 30-day window.
- 2Agree the target with the team, using current results and the selected benchmark as references.
- 3Review status and trend monthly and record what changed in the process each time the trend moved.
What this shows: The team has a target value and a consistent way to check progress each month.
FAQ
Why is my target stuck at not started?
No data has arrived for that metric in the evaluation window. Usually the underlying integration is missing — DORA targets need CI and incident data, coverage targets need a source that reports coverage.
What is the difference between built-in and custom benchmarks?
Built-in benchmarks are values supplied with the product. Custom values are ones you enter, for example from previous team results. Check the source and suitability of a benchmark before comparing it with your service.
Tips
- Progress calculation accounts for direction and targets of zero. Projections continue the trend from the last measurement date; they are assumptions, not promised deadlines.
- Choose a few priorities that the team can follow up on regularly.
- When a target is reached, save the result and discuss whether to set a new target or maintain the current level.