# 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.

[View your metrics](/content/signin/index.html) [Explore the signals](/content/features/metrics#metric-view/index.html)

## Six supported metrics 30–365 day windows

### Engineering metrics

#### Payments team

**Past 30 days**

- **Deployment frequency**: Elite 1.4/day
- **Review turnaround**: High 7.6h
- **Review governance**: Improperly reviewed merges High 1 PR
- Independently reviewed Selected window

*Illustrative values shown for a selected workspace window*

## 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.

### Metrics view

- **Deployment frequency**: Average successful production deployments per day. Higher is better.
  - Value: 1.4/day
- **Lead time**: Median time from PR creation to successful production deployment.
  - Value: 3.2 days
- **Review turnaround**: Median time from pull-request creation to the first human review.
  - Value: 7.6h
- **Improperly reviewed merges**: PRs merged without reviewers or merged by their own author.
  - Value: 1 PR
- **Stale PRs**: Open, non-draft pull requests that have not been updated recently.
  - Value: 4 PRs
- **Failed deployments**: Failed or errored production deployments. Cancelled runs are excluded.
  - Value: 0

## 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.

### Review flow

- **Pull-request responsiveness**: See how quickly review begins and where open pull requests are becoming stale.

### Review governance

- **Merge discipline**: Surface pull requests merged without independent review or by their own author.

## 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 High
  - Day 1 Day 10 Day 20 Day 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

| 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](/content/signin/index.html)