A single 'productivity score' is seductive. One number, one chart, one ranking. It is also almost always wrong — and often harmful once it touches performance conversations.
Healthy teams need signals about friction in the environment, not league tables of output. That is the design principle behind how DevInsights thinks about team health.
The problem with 'productivity'
Lines of code, commits per day, and PRs merged reward noise. They punish deep refactoring, thorough review, and the unglamorous work of making the next change cheaper.
When these proxies tie to performance reviews, teams optimize for the metric. PRs fragment. Reviews get rubber-stamped. The chart goes green while quality and morale go elsewhere.
Measuring the environment
We measure friction: focus time interrupted by review load, review burden shared unevenly, PRs left stale on the same authors week after week. None of these are stack-rank metrics.
When DevInsights flags someone as Watch, it is usually because they have carried the squad's review load, or their PRs are consistently the ones waiting longest. The right response is redistribution and calendar protection, not a performance plan.
- Focus time: are deep-work blocks getting shredded by review interrupts?
- Review load: is one engineer carrying a disproportionate share?
- Stale ownership: are the same PRs aging on the same people?
How managers should use it
Use health signals in 1:1s as questions, not accusations. 'I noticed your review load spiked — is that sustainable?' beats 'Your number is red.'
Never export team health to HR systems. The moment it becomes input to ratings, the data stops being honest.
Key takeaways
- LOC and commit counts are terrible proxies for impact.
- Measure environment friction — focus, review load, stale PRs — not people.
- Watch signals are for unblocking, never for stack ranking.
