The Team Overview tab is a per-member execution table. Each row is a teammate; each column is a metric you choose. This article explains what each column means and how to read the table without micromanaging.
What the table is for
Spot workload imbalance — who is overloaded and who has headroom.
Investigate cycle-time outliers at the individual level.
Catch process-mapping issues that only show up per member, such as one person's items always skipping a workflow state.
It is not a performance ranking. Reading it that way produces noisy, unfair conclusions and damages trust.
The columns
You pick which of these to show. They fall into two families.
Flow — how work moves through the board
Column | What it holds |
Throughput | items completed in the period |
WIP | items in flight — a snapshot, not an average |
Assigned Tasks | items assigned, regardless of state |
Avg Member Cycle Time | average cycle time of items this person completed |
Avg Member WIP Age | how long this person's in-flight items have been open |
Waiting Time | hours spent in statuses mapped to the Waiting category |
Done Active Time | active time accrued by completed items |
Working Time | elapsed time across active states |
Active Days | days this person did enough to count — see below |
Estimated Hours | sum of estimates on completed items |
Estimated vs Executed | estimate against actual, as a percentage |
Invested Hours | hours logged in the period |
Story Points | sum of story points on completed items |
Sprint Efficiency | completed work as a share of committed work |
Reworked Tasks | items that went backwards in the workflow |
Code — what happens in the repositories
Column | What it holds |
PRs Created | pull requests this person opened |
Reviews | review interactions on other people's pull requests |
Commits | commits authored |
PR Comments | comments left on pull requests |
Avg Member Time to Merge | from opening their own pull request to merging it |
Avg Member Review Time | from someone else's pull request opening to this person's first action on it |
Avg Member TT First Approval | time to the first approval on their pull requests |
Every column also shows its change against the preceding period.
Two columns that don't mean what they look like
Active Days is not "days they touched something". A day counts only when the person accumulated at least two recorded actions, and the actions come from several places — commits, pull requests, reviews, task status changes, logged hours and recorded interactions such as chat and calendar. Somebody who made one commit on a Tuesday and nothing else has not had an active day. The threshold is configurable by the environment, so check with your administrator before reading a specific number as gospel.
Reviews counts interactions, not reviews. Each comment on a pull request counts one, a commit pushed to someone else's pull request counts one, and only the first approval counts. Ten comments on one pull request read as ten. So a talkative reviewer outranks a thorough one, and somebody who only approves looks nearly inactive.
How to read the table without overreacting
Compare each member to the team's median, not to each other.
Always check the work mix. Different role mixes — engineering versus design, infrastructure versus product — drive different numbers.
Investigate, don't accuse. A high WIP age usually means a stuck item, not an unproductive person.
When a number looks wrong, suspect the board status mapping first. Most of the flow columns are derived from status categories, so an unmapped status moves several columns at once.
Related articles
Performance Delivery dashboard
Throughput
Cycle Time
Work in Progress (WIP)
Waiting Time
Review latency
Review participation