Elite
Deployment frequency
Average successful production deployments per day. Higher is better.
Value
1.4/day
Feature
Metrics
Engineering metrics your team can explain
Read six delivery and review signals through a consistent rating scale, using one selected window across the whole view.
Six supported metrics 30–365 day windows
Engineering metrics
Payments team
Deployment frequency
Elite1.4/day
Review turnaround
High7.6h
Review governance
Improperly reviewed merges
High
1 PR
Independently reviewedSelected window
Illustrative values shown for a selected workspace window
Metric view
Six signals in one selected window
Keep units specific to each metric while using the same Elite, High, Medium, or Poor scale across the view.
30d90d180d365d
High
Lead time
Median time from PR creation to successful production deployment.
Value
3.2 days
High
Review turnaround
Median time from pull-request creation to the first human review.
Value
7.6h
High
Improperly reviewed merges
PRs merged without reviewers or merged by their own author.
Value
1 PR
Medium
Stale PRs
Open, non-draft pull requests that have not been updated recently.
Value
4 PRs
Elite
Failed deployments
Failed or errored production deployments. Cancelled runs are excluded.
Value
0
Illustrative workspace values and trend lines
Metric taxonomy
Metrics engineering managers can defend
Each signal has a concrete definition, a native unit, and a clear direction of improvement.
Delivery
Release pace and reliability
Understand how often code reaches production, how long it takes, and when it fails.
deployment_frequencylead_timefailed_deployments
Review flow
Pull-request responsiveness
See how quickly review begins and where open pull requests are becoming stale.
review_turnaroundstale_prs
Review governance
Merge discipline
Surface pull requests merged without independent review or by their own author.
improperly_reviewed_merges
Reading the view
Trends with the metric context beside them
The visual hierarchy keeps the value, rating, selected window, and metric definition together.
Review turnaround
Example 30-day trend
7.6h
HighDay 1Day 10Day 20Day 30
Metric context
Review turnaround
Median time from pull-request creation to the first human review. Lower values indicate a faster review response.
Window
30 days
Direction
Lower is better
The chart is an illustrative trend visualization; values on this page are examples.
Rating guide
One readable scale, metric-specific thresholds
Deployment frequency rewards a higher value. Lower values are better for the other five metrics.
| Metric | Elite | High | Medium | Poor |
|---|---|---|---|---|
| Deployment frequency | ≥ 1/day | ≥ 1/week | ≥ 1/month | < 1/month |
| Lead time | < 1 day | < 1 week | < 1 month | ≥ 1 month |
| Review turnaround | < 4 hours | < 24 hours | < 3 days | ≥ 3 days |
| Improperly reviewed merges | 0 | 1–2 | 3–5 | > 5 |
| Stale PRs | 0 | 1–2 | 3–5 | > 5 |
| Failed deployments | 0 | 1–2 | 3–5 | > 5 |
Put your delivery signals in one view
Connect your workspace to calculate the six supported metrics from your own delivery activity.
View your metrics