Activity distribution shows how engineering activity — commits, pull requests, reviews, comments — spreads across the team. It's not a productivity ranking; it's a fairness and resilience signal.
What it measures
The relative share of total team activity attributable to each member, grouped by activity type (commits, PRs opened, reviews left, comments).
How Leanmote calculates it
share(member, type) = activity(member, type) / total_activity(team, type)
Per-activity-type so you don't conflate code authorship with review labor.
Reported as percentages and as a Gini-style concentration index when available.
How to interpret it
Even distribution within ±2× of the team median is healthy. Some variance is natural.
Heavy concentration in one or two members is a fragility signal — what happens if they leave?
Watch for type-specific imbalances: one person doing all the reviewing while authoring little is sustainable for a quarter, not for a year.
What to do about it
Rotate reviewer assignments to spread review load.
Pair contributors who rarely cross paths so knowledge diffuses.
For onboarders with low activity, pair them with mentors and remove blockers — low share early is normal but should trend toward team median over a quarter.
Related metrics
Review participation
Review latency
Team Collaboration Network — overview