Cross-Team Review %
Architect & Collaboration Metrics
%
Shows the percentage of your reviews that are for other teams.
💡 Like tracking what share of your teaching happens outside your own classroom, cross-team review percentage shows how broadly you contribute.
What It Measures
Shows the percentage of your reviews that are for other teams.
Why It Matters
Measuring collaboration breadth across organizational boundaries
Tracking knowledge sharing beyond your immediate team
How It's Calculated
Divides cross-team reviews by total reviews and multiplies by 100.
100 × prs_reviewed_cross_team ÷ (prs_reviewed + prs_reviewed_cross_team)Concrete Example
If 8 of your 20 total reviews this month were for other teams, your cross-team review percentage is 40%, you're a significant contributor beyond your own team.
What Does a Healthy Score Look Like?
Some cross-team review is healthy, but in-team coverage should come first.
Healthy
10–30% of reviews cross-team
Watch Out
Under 5% (siloed) or over 60% (neglecting own team)
Needs Attention
Near zero consistently, no cross-team collaboration
What Moves This Metric?
Goes up when…
Platform or shared infrastructure work crossing team boundaries
Domain expertise causing other teams to request your review
Open review culture encouraging cross-team engagement
Goes down when…
High in-team review volume consuming all review bandwidth
Strong team code ownership policies limiting external reviews
Low overall PR volume from other teams in your domain
Start Tracking Cross-Team Review %
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