Work in process (WIP) limits control how much work is undertaken simultaneously. In knowledge work such as software delivery, starting too many tasks at once creates hidden queues, context switching, delays, and reduced quality. Although activity appears high, actual throughput of completed value declines.
Effective WIP management shifts the focus from starting work to finishing it. By constraining concurrent work, bottlenecks become visible, flow improves, and teams deliver more predictably. Mature organisations treat WIP limits as a systemic tool for optimising the entire value stream rather than a local team practice. At the highest level, WIP is dynamically managed to maintain smooth, sustainable delivery aligned with customer priorities.
Description
There are no explicit limits on how much work can be in progress. Teams and individuals take on tasks continuously, leading to overload.
Observable Characteristics
Outcomes & Risks
Description
Teams recognise overload but manage it reactively without explicit limits or shared policies.
Observable Characteristics
Outcomes & Risks
Description
Teams establish clear limits on concurrent work, encouraging completion before starting new tasks.
Observable Characteristics
Outcomes & Risks
Description
WIP limits are adjusted based on measured outcomes to optimise throughput and reduce delays across the value stream.
Observable Characteristics
Outcomes & Risks
Description
WIP is managed across the entire value stream in real time, enabling rapid adjustment to changing priorities and conditions.
Observable Characteristics
Outcomes & Risks