What are Flow Metrics?

Flow metrics help teams understand how work moves through a system. Clear definitions and consistent start and finish boundaries make the measurements useful for conversations about queues, predictability, and capacity.

Why it matters

They help teams spot waiting, aging work, and excess demand without treating individual busyness as progress.

How it works

Work in progress (WIP): items that have started but have not finished. Throughput: items completed during a defined period. Work item age: elapsed time since an unfinished item started. Cycle time: elapsed time from an item's start to its finish.

Flow efficiency is another measure some teams use: active working time as a proportion of total elapsed time. It depends on a clear definition of active work and can help reveal waiting, but is not a substitute for examining the workflow.

Review distributions and patterns rather than relying on a single average. Define the kinds of work being compared, inspect blocked or aging items, and use the measures to decide which change to test.

Example

Consider a service team completing ten requests a week while forty remain in progress. A throughput chart alone looks reassuring, but work item age reveals that several requests have barely moved. The team maps waiting points and finds a review queue shared with another department. It limits new starts, helps finish the oldest requests, and agrees on a review policy with that department. It then watches work in progress, age, cycle time, and throughput together. If waiting falls while quality holds, the change is useful. The metrics guide investigation and improvement instead of becoming individual productivity targets.

Common misunderstanding

A higher throughput count can look like improvement even when work has been split into smaller items, easier requests are favored, or defects create additional tickets. Likewise, a shorter average cycle time can hide a growing tail of requests that wait far longer.

Keep measurement boundaries and work categories clear. Examine distributions, aging work, quality, and customer outcomes together. Use the metrics to ask where the system needs attention; turning them into individual targets can encourage behavior that improves the numbers while damaging delivery.

Further reading

The Kanban Guide: flow metrics

Related terms

Kanban · Systems Thinking · Outcome-Based Planning

To put this into practice, explore Getting Started With Kanban Journaling on nuAgility's learning platform.