WIP capacity ratio
Also known as WIP-to-capacity ratio, Concurrent work ratio
Definition
A WIP capacity ratio compares the amount of work currently in progress with a stated capacity measure, such as active processing slots or typical concurrent work. It is a diagnostic signal, not a universal target.
Compare unfinished work with room to process
A WIP capacity ratio can show whether the amount of unfinished work is small, near, or far above the system's normal processing capacity. The ratio is meaningful only when WIP and capacity share a boundary. A count of pull requests should not be casually divided by headcount.
A concrete example
An illustrative review process usually has room for four concurrent changes, but eight are waiting or active in review. A ratio of 2.0 signals pressure under that policy. The next question is whether to reduce intake, improve review capability, or split work differently.
Use it with flow outcomes
Inspect age, cycle time, queue time, and throughput before acting. A high ratio may be a temporary release event or a persistent constraint. A low ratio may reflect missing demand or a hidden queue elsewhere.
Limitations
Concurrency capacity is difficult to define for knowledge work and changes with item complexity. Avoid cross-team rankings. Use a local baseline and document how the numerator and denominator were built.
How this relates to Weave
Weave can help teams examine unfinished change activity and delivery patterns that inform a WIP discussion. Its view may not include every non-code item or capacity constraint, so use the ratio as a prompt to inspect the complete workflow.
Explore Engineering intelligence