Knowledge Sharing Index
Extended Metrics for Engineering Managers
score
Unique to Projcity
Measures how broadly review responsibilities are distributed across the team.
đĄ Like a teacher's impact score, it rewards both how evenly the teaching is distributed AND how much teaching is happening overall.
What It Measures
Measures how broadly review responsibilities are distributed across the team.
Why It Matters
Highlighting collaboration depth and knowledge spread
Ensuring multiple team members are engaged in code review
How It's Calculated
Multiplies review load fairness by the sum of approvals and comments.
review_load_fairness Ă (approvals + comments)Concrete Example
A team with a review load fairness score of 0.80 and 50 total review actions has a knowledge sharing index of 40, the higher the number, the more broadly knowledge is spreading.
What Does a Healthy Score Look Like?
Higher is better, low scores mean knowledge is siloed in a few people.
Healthy
Growing quarter over quarter
Watch Out
Stagnant or declining
Needs Attention
Very low with high review concentration, critical knowledge silos
What Moves This Metric?
Goes up whenâŠ
More team members actively participating in code review
Distributed review assignments preventing load concentration
Team culture encouraging all members to review across the codebase
Goes down whenâŠ
Only senior engineers reviewing code, creating single points of failure
Domain knowledge siloed, certain code only reviewed by one person
Low overall review activity reducing the total spread
Start Tracking Knowledge Sharing Index
Connect GitHub and Shortcut in minutes. All metrics update automatically.
Engineering metrics and developer well-being platform. Track 50+ metrics, AI-powered insights, and Dynamic Archetypes for just $10/active user/month.
contact@projcity.com