Benchmarking in Span
Last updated: November 12, 2026
Benchmarking in Span compares your engineering metrics against a reference group: the industry, your whole organization, or part of it, such as one job level, job title, or team. It answers "is this number actually good?" Is a 2-day PR cycle time fast or slow? How does our deployment frequency compare to other teams?
Why it matters
Set realistic goals: use P50, P75, and P90 to define what "good" and "great" look like, grounded in real data.
Find improvement areas: spot where you sit consistently below the median.
Recognize wins: see when teams perform in the top quartile or top decile.
Compare like with like: a team of senior engineers can be compared with senior engineers across your organization, not with everyone.
Support executive conversations: benchmark data gives leaders a credible frame for discussing performance.
How it works
Choose the comparison with the Benchmark button in the filter controls of a report or metrics page. The button needs the Benchmarking permission, which Owners, Admins, Managers, and Team Leads have by default. The menu has two sections, Industry and Company:
Menu option | What you're compared against | Availability |
|---|---|---|
Industry | People across Span customer organizations that share data for industry benchmarks. On charts, this section is titled Industry reference line and offers P50, P75, and P90. On tables and ranks it shows a single Industry option, because a rank uses the whole industry distribution. | Span turns this on for your organization on request, and your role also needs the Industry Benchmarking permission (Owners, Admins, and Managers by default). When both are in place, Industry is the default on most pages. |
Organization (under Company) | Everyone in your organization that the metric covers. | Every organization. It's the default when Industry isn't available. |
Job level › | People at the job levels you check. | Submenus under Company. Each appears only when the page supports it and your roster has values for it. Job level benchmarking works only if job levels are populated for users in your roster. Some pages also offer Job family. |
Job title › | People with the job titles you check. The list shows every job title in your organization. | |
Person Is Manager › | People who manage others, or people who don't. | |
Team › | People on the teams you check. |
In the submenus you can check several values, and combine values across submenus, to narrow the Company group. Checking a value switches the benchmark to Company. The button shows your current choice, for example "Benchmark: Org", "Benchmark: Ind. P50", "Benchmark: Industry", or the values you checked, such as "Benchmark: Senior - Platform". If a page shows no Benchmark button, its metrics don't support benchmarking or your role doesn't have the Benchmarking permission.
How Span calculates the benchmark
Industry reference line: the line sits at the percentile you pick in the industry distribution. P50 is the median; P75 is better than 75% of the population; P90 is better than 90%. For metrics where lower is better, Span flips the scale, so P90 still means top-decile performance.
Company reference line: the line is the chosen group's own value for the period, calculated the same way as the metric, not a median. For example, with Job level = Senior on PR cycle time, the line is the cycle time of all PRs by senior engineers, using your page's aggregation. Count metrics such as total PRs merged don't draw a Company line, because a period total would sit far above the weekly points.
Colored dots and ranks: Span ranks each value against the distribution of the same metric across the chosen group, using the same kind of rows the table shows: people against people, teams against teams. The P50 / P75 / P90 choice doesn't change the dot.
Industry data: Span builds the industry distribution from person-level values in participating organizations. It publishes a metric for a period only when it has at least 300 data points, and caps extreme values at the 5th and 95th percentiles. If there's no industry data for a metric and period, no Industry line or rank appears.
Colored dots: each dot shows your percentile rank within the chosen group.
Dot | Level | Percentile range |
|---|---|---|
Red | Worst | 0–20th |
Orange | Bad | 20–40th |
Yellow | Average | 40–60th |
Light green | Good | 60–80th |
Dark green | Best | 80–100th |
Span accounts for metric direction. For metrics where higher is better (such as PRs merged / week), a higher rank is greener. For metrics where lower is better (such as PR cycle time), the scale is reversed, so green always means good. Neutral metrics aren't reversed.
Where you'll see benchmarks: report pages, team and individual pages, and the Comparison report under AI insights, which compares against your organization only. Metric digest emails rank against a Company group: Organization, or the Company values saved with the digest. They don't use Industry. DX survey question and theme pages have their own Compare to picker, which includes the Span Benchmark, a fixed survey benchmark dataset.
Setup
Open a report or metrics page and click the Benchmark button in the filter controls.
To compare with the industry, pick P50, P75, or P90 under Industry reference line (or Industry on table pages).
To compare with your whole organization, pick Organization under Company.
To compare with part of your organization, hover Job level, Job title, Person Is Manager, or Team under Company and check one or more values. The menu stays open so you can check several.
Note: If you can't benchmark by Job level, make sure job levels are populated for users first. Level-based benchmarking will not work if those roster values are missing, even when benchmarking access is enabled.
If you don't see Industry, ask your Span account team to turn it on, and check with your Span admin that your role has the Industry Benchmarking permission.
Things to know
The benchmark group is separate from your page filters. Filtering a page to one team changes the values you see, not the comparison group. The Organization benchmark still uses your whole organization until you narrow it in the Benchmark menu.
Worked example. You filter Delivery to the Platform team, whose PRs merged / week is 3.0. With Benchmark: Org, the chart line sits at your organization's overall value, 4.0, so Platform is below it. You open Job level › and check Senior, because Platform is mostly senior engineers. The line moves to the senior engineers' value, 3.2, and Platform's dot is now ranked against senior engineers only, so the same 3.0 can land in a different color band. You then pick P75 under Industry reference line, and the line moves to the industry's 75th-percentile value for that metric and period.
The same value can change color when you switch the group, because your rank changes.
Small groups give coarse comparisons. Span sets no minimum size for a Company group. A group of two or three people, such as a rare job title, gives a benchmark that sits close to those people's own values and moves a lot from period to period. Prefer larger groups, or Organization, for decisions.
Company groups include everyone in them. A Company benchmark covers every person in the group, including people whose individual data you can't see. Span shows only the benchmark value and your rank, not their individual values.
Percentiles move over time. As your organization and the industry pool change, thresholds recalculate, so compare ranks within a period rather than across distant periods.
Start internal, then go external. Organization benchmarks show relative strengths across your teams; Industry adds outside context.
P50 as a baseline, P75 as a target works for many teams. Top-decile performance often reflects very specific contexts, so don't over-index on P90.
Pair benchmarks with context. Below P50 isn't automatically a problem. Combine benchmark data with retrospectives, surveys, and team conversations.
Related articles
Why metric values differ between views
How to read Span's "/ week" metrics
Need help?
Contact your Span account team or reach out to support@span.app.