Navigara

How Top Engineering Teams Actually Perform

A live index of the industry's leading engineering orgs. Every commit is weighted by the work it represents, not the lines it touched, and reported as ETV per engineer.

+1,798engineers' worth of capacity,
nobody hired

2,371 engineers needed at the pre-AI baseline
Engineering capacity added per org
real engineerscapacity, not headcount1 mark = 10 engineers
Rows come to +1,862, the index reads +1,798. They are not meant to agree. Why?
Each org is measured against its own first reading and the index against its own, so the parts do not add up to the whole. The index also divides pooled output by the pooled engineer set, deduplicated across orgs and covering every team in the index, including ones without a public row.
Capacity added since the index's own first reading, measured from shipped output. How to read it
Every org row is measured against its own first reading, not a shared one. The figures come from shipped output, not from AI usage: teams also changed size, tooling and composition over this period.

How fast did it happen?

ETV per engineer, rolling 90 days. Each series starts from its own pre-AI baseline, so read a curve against where it started, not against its neighbours.

Show methodology

Where does each org stand?

Same measure, one card per org. Headcount is not the story, the multiple per engineer is.

Speed tells you how much a team ships. It doesn't tell you what.

Direction

Faster at what?

The same amount of output can be new features, or fixes to work that already shipped. The mix is the decision.

Performance Composition

How each org's ETV splits across features, maintenance, tests, docs, and fixes.

Patterns

Where does the output come from?

The same measure one level down, at the codebases the output is actually made in. Ranked by per-engineer ETV, this week against the full quarter.

Your turn

Where does your team stand?

The index measures public repositories. The same measure runs on private ones.