How much of the work is net-new
The Growth slice is the share of Engineering Throughput going into new functionality — features, capabilities, expansion. A rising Growth share means the team is spending a larger fraction of its energy on what users will recognise as a new product, not on running the existing one.
GROWTH SHARE BY DAY
Each bar is one day's growth share — that day's Growth ETV divided by total ETV. The line is the 90-day trailing rolling average — the underlying trend.
Baseline
32.5%
90-day rolling avg ending 2025-04-01
Latest
36.9%
90-day rolling avg ending 2026-05-27
Change (percentage points)
+4.4 pp
from 32.5% to 36.9% across the 90-day rolling series
How to read it
Faint barsare each day's raw Growth share (that day's Growth ETV divided by total ETV). The bold line is the 90-day trailing rolling average — that's the trend you want to read.
The headline is the change in percentage points between the first and the most recent endpoint of the 90-day rolling-average line — i.e. the leftmost and rightmost points the chart actually plots, not a calendar-quarter average. We use percentage points (pp) rather than a relative % because both sides are already percentages.
Why it matters
Growth share is the cleanest answer to "what is the team actually shipping?". Two teams with identical headline Performance can spend it very differently — one on new product, one on patching old.
Top-quartile orgs in this benchmark sustain Growth share in the 30–45% range. Below 20% for sustained periods usually means a maintenance backlog has crowded out feature work.
How we measure growth share change, and how to read the trend.
Show methodologyHide methodology
How we measure growth share change, and how to read the trend.
Show methodologyHide methodologyWhat counts as Growth
Commits that add new capability — new endpoints, new screens, new flags wired to net-new logic, new packages. We classify with a combination of file diff semantics and conventional-commit style metadata. Refactors that don't add capability land in Maintenance.
How shares are computed
For each day we sum the Engineering Throughput of merged commits, split by category, and divide by the daily total. The rolling-average overlay is a 90-day trailing mean. The most recent day is dropped if it looks like a partial sync.
How the change is computed
We compare the first and the most recent point of the 90-day rolling series — the leftmost and rightmost values of the bold line on the chart — and report the difference in percentage points. Both endpoints are single 90-day rolling readings, not calendar-quarter averages, so they stay aligned with the rest of the site's rolling-90d convention.