Skip to main content

Review participation

Share of teammates who regularly review each other's pull requests.

Review participation answers one question: is code review spread across the team, or carried by two people? Leanmote has no single number for it — there is no participation percentage to look up. What it has is the data to answer the question in about thirty seconds.


​

Where to read it


​

Open the Team Activity table and add the Reviews column. Every member of the selected team gets a row, so "who participates in review?" becomes "how many of these rows are above zero?".


​

What counts as a review


​

A review is any of three actions on a pull request the person did not author:


​

  • a comment — each one counts separately, so ten comments on one pull request count as ten

  • a commit pushed to that pull request

  • the first approval on it, and only the first — later approvals are not counted


​

Pull requests you authored are skipped entirely, so nobody's own work inflates their count.


​

Two consequences worth holding onto. A talkative reviewer will outrank a thorough one, because comments are counted one by one. And somebody who only approves will show a far lower number than somebody who comments, even when they read the same amount of code.


​

How to interpret it


​

These are rules of thumb. Leanmote does not flag any of them.


​

  • Two or three rows above zero on a larger team means review is concentrated. Watch for senior burnout.

  • Most of the team above zero is healthy — participation without it being mandatory busywork.

  • Everybody at exactly one or two can mean rubber-stamp approvals rather than genuine engagement. Open the drill-down and look at the review type: all Approval and no Comment is the signature.


​

What to do about it


​

  • If participation is concentrated, distribute reviews via auto-assignment or a rotating reviewer rota.

  • Pair junior engineers with seniors so review skills spread.

  • Surface review activity in 1:1s — sometimes participation is invisible because nobody notices it.


​

Related metrics


​

  • Review latency — how long people take to pick a review up

  • Time to First Approval

  • Responsiveness — how long the author takes to answer a reviewer

  • Activity distribution

Did this answer your question?