24 Work in Progress and Flow Control

Work in Progress and Flow Control is the discipline of deliberately managing how much work a team is actively handling at any given time, and how that work moves through the stages of a workflow, in order to minimize delays, expose bottlenecks, and maintain a steady, predictable rate of completed output.

Why Work in Progress Requires Active Management

The cost of excessive parallel work

When a team takes on more concurrent work than it can effectively handle, individual items spend increasing amounts of time waiting rather than being actively worked on, attention is divided across too many competing priorities, and the time required to complete any single item lengthens even though the team appears fully occupied.

Little's Law and the relationship between flow variables

This relationship, known as Little's Law, formalizes a core insight of flow control: for a given rate of completing work (throughput), the average time an item takes from start to finish (cycle time) rises directly with the amount of work in progress, meaning that reducing work in progress is one of the most direct ways to reduce how long individual items take to complete.

Work-in-Progress Limits

Setting explicit limits per workflow stage

Flow control commonly involves setting an explicit maximum number of items permitted in each stage of a workflow at once; when a stage reaches its limit, no new item may enter that stage until an existing item moves out, creating a structural constraint that prevents work from silently accumulating in any single part of the process.

Encouraging completion over initiation

Because reaching a work-in-progress limit blocks starting new work, team members whose own tasks are complete are naturally encouraged to help finish existing in-progress items elsewhere in the workflow rather than beginning something new, reinforcing a collective focus on completion over the appearance of broad individual activity.

Identifying and Managing Bottlenecks

Recognizing accumulation points

When items consistently accumulate at, or wait unusually long before, a particular workflow stage, this signals a bottleneck — a point in the process whose capacity is insufficient relative to the rate at which work arrives from earlier stages, regardless of how efficiently other stages may be operating.

Responding to a bottleneck

Once identified, a bottleneck can be addressed by reallocating capacity toward it, reducing the amount of work released into the stages upstream of it so as not to worsen its backlog, or restructuring the workflow itself to reduce dependency on the constrained stage, rather than attempting to speed up unrelated parts of the process that are not actually limiting overall flow.

Visualizing Flow Over Time

Cumulative flow diagrams

Plotting the cumulative count of items in each workflow stage over time produces a set of bands whose relative widths indicate the amount of work accumulated at each stage and whose slopes indicate the rate of arrival and completion, providing a visual tool for detecting growing work-in-progress or slowing throughput before they become severe.

Interpreting widening or narrowing bands

A widening band between the count of started and completed items indicates growing work in progress and lengthening cycle times, while a stable or narrowing band suggests the team is completing work roughly as quickly as it is being started, making the diagram a useful diagnostic for whether flow control measures are functioning as intended.

Balancing Flow Control With Practical Constraints

Setting limits appropriate to team size and work variety

Work-in-progress limits set too loosely fail to meaningfully constrain overloading, while limits set too tightly can leave team members idle when their specific expertise is not needed by any currently available item; determining appropriate limits typically involves observation and adjustment based on actual team composition and the variety of work being handled.

Accounting for legitimately necessary parallel work

Some work in progress reflects legitimate necessity, such as work intentionally paused pending external input; flow control practices generally distinguish between work in progress that is actively blocked for a valid external reason and work in progress that is merely proceeding slower than necessary due to poor prioritization.

Why Work in Progress and Flow Control Matters

Reducing delay without requiring more effort

By limiting concurrent work and directing attention toward completing rather than merely starting items, flow control can substantially reduce the average time work takes to complete without requiring the team to work harder, simply by reducing the waiting and context-switching costs inherent in juggling too many simultaneous items.

Making process problems visible

Explicit work-in-progress limits and flow visualization surface bottlenecks and process inefficiencies that would otherwise remain hidden behind the general impression of a busy, active team, supporting evidence-based process improvement rather than improvement efforts based on intuition alone.