Avg Member Cycle Time is the average time a single team member's items spent in active states before completing, 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(member) = sum(cycle_time(item)) / count(items) for items where assignee = member and completed_at in period
Aggregation — straight mean of per-item cycle times. Not a percentile.
Unit — hours.
Working vs calendar hours — calendar hours by default. A small set of organizations on a working-hours mode (Mon–Fri, 8h/day) get working-hours math instead, but the default for everyone else is calendar.
Bots and drafts — bot accounts are not auto-excluded from this metric. If you have system accounts that move items, exclude them in your team mapping.
Team-level aggregation note
When you see a team-level cycle-time number derived from per-member numbers, it's a mean of member means, not a pooled mean across every item. A small number of items per member can move the team number more than expected — read this metric next to Throughput to keep that in context.
How to interpret it
Higher than peers usually signals one of three things: harder items, more reviews and blocks, or unclear scope. The member's individual context matters.
Low Avg Member Cycle Time with low Throughput can mean the person picks up only small items.
Single-week swings are usually random; trust the trend across several weeks.
What to do about it
For consistently slow members, look at item mix and review queue first.
For consistently fast members, surface the working pattern; it's worth learning from.
Pair with Avg Member WIP Age to separate active-work slowdowns from stuck items.
Related metrics
Cycle Time
Avg Member WIP Age
Throughput