Avg Member Cycle Time is the average time it takes a single team member to move an item from active start to done, computed across the items they completed in the period.
What it measures
The same Cycle Time metric, scoped to one person's completed items.
How Leanmote calculates it
avg_member_cycle_time = avg(completed_at - in_progress_at) for items where assignee = member and completed_at in period
Active states only — backlog and "to do" time aren't counted.
Best read with the team median next to it. A member 2× the team median is worth investigating; ±20% probably isn't.
How to interpret it
Higher than peers usually signals one of three things: harder items, more reviews/blocks, or unclear scope. The member's individual context matters.
Low Avg Member Cycle Time with low Throughput can indicate the person picks up only small items — possibly a coaching opportunity.
Watch trends, not single periods. Single-week swings are usually random.
What to do about it
For consistently slow members, look at their item mix and review queue first. Fix process before assigning behavioral conclusions.
For consistently fast members, surface the working pattern — they're probably worth learning from.
Pair with Avg Member WIP Age to see whether the slowdown is in active work or in stuck items.
Related metrics
Cycle Time
Avg Member WIP Age
Throughput
Team Overview tab — what each metric tells you