Review queue pressure

What the measure captures

Review queue pressure is the condition in which pending review work consumes more capacity than the responsible reviewers can sustainably provide. It is not the same as a large queue at one instant. Pressure becomes more credible when arrival rate stays above completion rate, queue age rises, or specialist requests repeatedly wait beyond the team’s normal range. Define the review stage carefully because requests waiting for first feedback are different from changes waiting for a final approval.

A practical example

Suppose a platform group receives ten review requests in a week and completes seven, while three older requests remain open. The group may feel busy even if the total queue looks modest. Segmenting the requests by repository, risk class, and owner can show whether one specialist is the constraint. A temporary response may be to pause new discretionary work, clarify priority, and ask a backup reviewer to help with safe categories.

How to use it carefully

Pressure is a team-level operating signal, not a justification for rushing approvals. Capacity can be reduced by incidents, leave, unfamiliar code, or review work that requires deep investigation. Compare queue pressure with review quality samples, rework, and escaped defects. Avoid converting an inferred capacity gap into a productivity judgment about an individual reviewer.

How this relates to Weave

Weave can connect review queue signals with change context, review time, and delivery flow so teams can investigate pressure at the system level. It does not prescribe staffing or replace reviewer judgment. Use the evidence to improve ownership, sequencing, and review conditions.