Activity distribution is not a separate screen. It's what you read across the Team Activity table, where every metric is broken out person by person. Treat it as a fairness and resilience signal, not as a productivity ranking.
What it measures
Team Activity puts each member of the selected team on a row and each metric you pick on a column. Among the metrics available are commits, pull requests created, reviews and PR comments — alongside throughput, work in progress, active days, reworked tasks, invested hours and story points.
The distribution is the shape of a column: who accounts for most of it, and who barely appears.
How Leanmote calculates it
Leanmote does not compute a share. Each cell holds that person's own count for the period, in the unit of the metric — commits, reviews, comments, merge requests, tasks, hours or story points. Only two of the metrics are already percentages: sprint efficiency and estimated vs executed.
So the proportion a person represents is something you read off the column, not a number the product reports. There is no concentration index behind it either.
One thing the table does compute for you is the comparison against the preceding period, so a column tells you both who carries the work today and whether that changed.
How to interpret it
These are rules of thumb for reading the column. Leanmote does not flag any of them.
Even distribution, with nobody at several times the team median, is healthy. Some variance is natural.
Heavy concentration in one or two people is a fragility signal — what happens if they leave?
Watch for imbalances between metrics rather than within one: somebody 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 — a low share early is normal, but it should trend toward the team median over a quarter.
Related metrics
Review participation
Review latency
Team Collaboration Network — overview