Commons Impact. The 4x Multiplier.
Shared utilities, libraries, and infrastructure code weighted 4x vs feature code. Reward engineers who build for the whole org, not just their team.
What You'll See
Key capabilities and insights available in this lens.
4x Multiplier
Code contributed to shared libraries, utilities, and infrastructure receives a 4x weight in activity scoring. Platform engineers are finally measured fairly.
Commons Detection
Review shared repositories and packages, then open the Repository Lens to inspect where teams use them.
Org-Wide Impact
Track how much of your codebase is built on shared infrastructure vs. isolated feature code. Healthy orgs have growing commons adoption.
Adoption Trends
Monitor commons adoption over time. See which teams are contributing to shared infrastructure and which are reinventing the wheel.
Platform Heroes
Surface the engineers who build the most impactful shared code. Recognize contributions that multiply across the entire organization.
Balance Metrics
Review shared contribution patterns alongside Code Balance and Bus Factor before deciding where to invest in shared infrastructure.
How Commons Impact is calculated
Commons Impact gives extra weight to work on shared code. A commit to a shared library, utility, or infrastructure repository counts 4 times; a commit to a feature repository counts once. The weighted total is the contributor's effective commits, which also feeds the Activity Score.
Effective commits = direct commits + (commons commits × 4)
- Contributors who do commons work get a Platform Impact line on their People Lens card that shows the inputs and the result, for example "138 direct + 29 commons = 254 effective".
- Commons covers shared libraries, utility packages, and infrastructure code that other teams build on. Feature code in a single product repository counts at normal weight.
- The Repository Lens also shows a Commons percentage for each repository, so you can see where commons work is concentrated.
| Contributor | Role | Direct commits | Commons commits | Effective commits |
|---|---|---|---|---|
| gael | Platform Engineer | 138 | 29 | 254 |
| priya | Staff Engineer | 92 | 41 | 256 |
How to read the numbers
- Compare effective commits, not raw commits. In the sample, gael: 138 direct + 29 commons × 4 = 254 effective commits, while priya: 92 direct + 41 commons × 4 = 256 effective commits. The second engineer made fewer commits but did more shared work, and ends up slightly ahead.
- Read repository Commons percentages against what each repository is for. In the sample, the shared library sits highest, shared-components at 89%, and a single-purpose service sits lowest, data-pipeline at 8%. Compare a repository with others of the same kind rather than with the whole list.
- Watch the trend over time. Rising commons adoption means more teams build on shared code instead of keeping private copies.
- Check concentration. If one engineer produces most of the commons work, the shared code has a bus factor problem even when its Commons percentage looks healthy.
Frequently asked questions
How is Commons Impact calculated?
Each commit to a shared repository, such as a common library, utility package, or infrastructure code, is counted 4 times. Effective commits equal direct commits plus commons commits multiplied by 4. The People Lens shows all three numbers on the contributor card so the calculation is visible.
Why are commons commits weighted 4x?
Code in a shared library is reused by every team that depends on it, so one change does work that would otherwise be repeated across many feature repositories. Raw commit counts hide that work, which makes platform engineers look less productive than they are.
Where does Commons Impact show up in the dashboard?
Per contributor, in the Platform Impact line of the People Lens card and as an input to the Activity Score. Per repository, as the Commons percentage in the Repository Lens. At the organization level, as Commons Growth in the Executive Lens.
Want to see this in your org?
Get early access to the full Organization Dashboard.