Avg Member Time to Merge is the average elapsed time from when a member opens a pull request to when it is merged. It tells you how long the end-to-end PR cycle takes for a single author's work.
What it measures
For PRs authored by this member and merged in the period: the average duration between opened_at and merged_at.
How Leanmote calculates it
avg_member_time_to_merge(member) = sum(merged_at - opened_at) / count(prs) for prs where author = member and merged_at in period
Aggregation — straight mean of per-PR durations.
Unit — calendar hours. Working-hours mode does not apply to this metric: weekend gaps and night gaps are included.
Scope — only PRs that were actually merged contribute. Closed-without-merge PRs don't count.
Bots and drafts — bot accounts are not auto-excluded. Use team mapping to keep system accounts out.
Team-level aggregation note
A team-level number derived from per-member values is a mean of member means, not a pooled mean across all PRs. A member with one extra-slow PR can move the team value more than they would in a pooled calculation.
How to interpret it
This metric mixes author behavior and review behavior — long times don't necessarily mean the author is slow; review pickup is often the bigger driver.
Compare against the team median. Outliers usually have a specific cause (a stuck PR, a complex change, a missing reviewer).
Use Submitter and Reviewer metrics to localize where the delay actually lives.
What to do about it
If review pickup dominates, set a team SLA on first review.
If author iteration dominates, coach toward smaller PRs and faster review-response cycles.
If approval-to-merge dominates, investigate the deploy/release process.
Related metrics
Lead Time for Changes
Avg Member Review Time
Avg Member TT First Approval