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_time_to_merge = avg(merged_at - opened_at) for prs where author = member and merged_at in period
Working hours can be respected so weekend gaps don't inflate the metric (configurable).
Median and P90 are also exposed alongside the mean.
Cancelled or unmerged PRs don't contribute.
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
Review latency
Avg Member Review Time
Avg Member TT First Approval