Cross-Team Reviews
Architect & Collaboration Metrics
Counts the number of pull requests you reviewed from other teams.
💡 Like being a guest lecturer in another department, cross-team reviews spread expertise and build relationships across the organisation.
What It Measures
Counts the number of pull requests you reviewed from other teams.
Why It Matters
Tracking cross-team collaboration
Measuring your broader codebase knowledge
How It's Calculated
Counts each review action where you and the author are on different teams.
COUNT(review_actions WHERE reviewer_team ≠ author_team)Concrete Example
If you reviewed 5 pull requests from other teams this month, you're contributing to cross-functional knowledge sharing and broader codebase awareness.
What Does a Healthy Score Look Like?
Some cross-team reviews are healthy, signals broad codebase knowledge.
Healthy
1–3 cross-team reviews per week
Watch Out
Zero cross-team reviews over multiple months
Needs Attention
Extremely high, may signal unclear team ownership
What Moves This Metric?
Goes up when…
Shared codebase components or platform work touching multiple teams
Senior engineers actively mentoring across team boundaries
Open review culture where any engineer can review any PR
Goes down when…
Strong team boundaries limiting review to within-team PRs
Specialised codebases where cross-team review adds little value
Heavy in-team review load leaving no bandwidth for cross-team work
Start Tracking Cross-Team Reviews
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