The Team Collaboration Network tab on the Performance Delivery dashboard shows how engineers interact with each other's work — who reviews whose pull requests, how quickly reviews land, and how activity distributes across the team.
What it surfaces
Review participation — what share of teammates regularly participate in reviews.
Review latency — how long PRs wait between open and first substantive review.
Activity distribution — how commits, reviews, and comments distribute across the team.
Together, these signals explain the social and operational reasons delivery is fast or slow, beyond what cycle time alone can show.
Why it matters
Review pickup is one of the largest contributors to Lead Time. Review latency is the most direct lever to pull on it.
Concentrated review load (one or two seniors carrying the team) is a fragility signal — track it before it becomes attrition.
Skewed activity distribution catches missing onboarding, knowledge silos, and informal hierarchies.
[SCREENSHOT: Team Collaboration Network with reviewer graph]
How to read this tab
Start with the network graph — who is reviewing whom?
Click Review Latency. If it's well above your team's working agreement, drill into who's slowest.
Inspect the activity distribution. Is the load even, or concentrated?
Pair findings with Performance Delivery's flow tab to see whether collaboration friction explains a cycle-time issue.
Related articles
Review participation
Review latency
Activity distribution
Performance Delivery dashboard