Work in Progress Measurement

Work in Progress Measurement is the practice of tracking how many items a team is actively working on simultaneously at any given point in time, providing a real-time indicator of the team's current level of parallel effort and a critical input for understanding why work may be moving more slowly than expected. It connects directly to both Cycle Time Measurement and Work Item Age Measurement, since the number of items concurrently in progress has a direct, mathematically demonstrable relationship to how long any individual item takes to complete.

What Work in Progress Represents

A Snapshot of Concurrent Effort

Work in progress, often abbreviated as WIP, is simply a count of how many items are currently in an active, unfinished state at a given moment, distinct from the backlog of items not yet started and from the pool of items already completed, isolating specifically the portion of work the team is presently engaged with.

A Measure That Changes Continuously

Because items are constantly starting and finishing, work in progress is inherently a moving figure rather than a fixed one, meaning it is typically tracked either as a series of point-in-time snapshots or as an ongoing running count updated whenever an item's status changes.

Why Work in Progress Matters for Flow

The Relationship Between WIP, Throughput, and Cycle Time

A well-established relationship in flow-based process theory connects these three quantities: the average amount of work in progress equals the average throughput multiplied by the average cycle time, meaning that for a given throughput, increasing work in progress necessarily increases average cycle time, and for a given cycle time, throughput is limited by how much work is in progress at once.

High WIP Tends to Slow Individual Items

When a team takes on too many items simultaneously relative to its actual capacity to make progress on all of them, attention becomes divided, context-switching increases, and individual items tend to sit longer between moments of active progress, extending their cycle time even though the team may feel busy throughout.

Limiting Work in Progress Deliberately

Setting Explicit WIP Limits

Many teams practicing flow-based methods set explicit maximum limits on how many items are permitted to be in progress at once, particularly within specific workflow stages, using the limit as a deliberate constraint that forces attention toward finishing existing items before starting new ones.

The Effect of a WIP Limit on Behavior

A binding WIP limit changes team behavior directly: when a stage reaches its limit, the team is prompted to address whatever is blocking progress in that stage, such as an item awaiting review, rather than starting new work and allowing the existing item to sit indefinitely.

Measuring and Visualizing Work in Progress

Point-in-Time Counts by Stage

The simplest form of measurement counts how many items currently sit within each stage of the workflow, offering a snapshot that reveals whether work is accumulating disproportionately in a particular stage relative to others.

Cumulative Flow Representation

Tracking these stage-level counts over successive time periods and stacking them together produces a cumulative flow view, in which the vertical thickness of each stage's band at any point in time directly represents the work in progress within that stage at that moment.

A Work in Progress Snapshot

The review stage, visibly exceeding the dashed WIP limit line while other stages remain within their own bounds, immediately identifies where the team's parallel effort has become concentrated, guiding attention to that specific stage rather than requiring a broader investigation.

Interpreting Work in Progress Alongside Other Metrics

High WIP as an Explanation for Rising Cycle Time or Age

When cycle time or work item age, as covered in their respective dedicated practices, begin trending upward, checking current work in progress is often the first diagnostic step, since a rise in concurrent active items is a common and directly explanatory cause of slower individual item completion.

Distinguishing Genuine Capacity Growth From Overcommitment

An increase in work in progress is not automatically undesirable if it reflects genuine growth in team capacity, such as new members joining, but distinguishing this from simple overcommitment requires checking whether throughput and cycle time have kept pace with the increased parallel effort or have instead begun to suffer.

Common Pitfalls

Equating Busyness With Productivity

Interpreting a high work in progress count as evidence of a hardworking, productive team overlooks the flow relationship demonstrating that excessive concurrent work tends to slow the completion of each individual item, often reducing overall throughput despite the appearance of constant activity.

Setting WIP Limits Without Enforcement

Establishing a WIP limit but allowing it to be routinely exceeded without any real response removes the limit's practical value, since its benefit depends specifically on the behavioral change it prompts once a stage reaches capacity.

Ignoring Stage-Level Detail in Favor of a Single Total

Tracking only the overall count of work in progress across the entire workflow, without breaking it down by stage, obscures exactly where concurrent work has become concentrated, weakening the metric's usefulness for identifying a specific bottleneck.