Definition
Flow Efficiency
Flow efficiency is the percentage of an item's total time that was spent actively worked on versus waiting. If an issue takes ten days from start to done but only two were hands-on, its flow efficiency is 20%. Most teams are shocked to find theirs is low — proof that delays, not slow work, dominate delivery time.
Key takeaways
- Flow efficiency is the percentage of an item's total time that was spent actively worked on versus waiting. If an issue takes ten days from start to done but only two were hands-on, its flow efficiency is 20%. Most teams are shocked to find theirs is low — proof that delays, not slow work, dominate delivery time.
- Flow efficiency divides active time by total elapsed time.
- Flow efficiency is therefore a diagnosis, not a target to maximize.
Flow efficiency divides active time by total elapsed time. The numerator is the time work was genuinely in progress; the denominator is the whole span from start to finish, including every wait — blocked on a dependency, queued for review, parked pending a decision. The resulting percentage exposes a truth that raw cycle time hides: how much of an item's life was spent moving versus stuck.
The numbers are usually humbling. Many knowledge-work teams discover flow efficiencies of 15% or less, meaning the vast majority of delivery time is waiting, not working. This reframes how to go faster. When 85% of the clock is idle time, hiring faster workers or pushing harder barely moves the total — the leverage is in attacking the waits: shrinking queues, clearing blockers sooner, reducing handoffs between specialists.
Flow efficiency is therefore a diagnosis, not a target to maximize. Pushing it toward 100% would mean eliminating all slack, which makes a system brittle. The useful move is to measure it, see where the waiting concentrates, and remove the worst delays — which is exactly what limiting WIP and tightening handoffs accomplish, pulling cycle time down by attacking idle time rather than active time.
Related terms
- Cycle TimeCycle time is how long an issue takes from the moment work actively starts on it to the moment it is done. Measured in hours or days, it captures the team's hands-on flow efficiency. Shorter, more consistent cycle times mean a more predictable system — the core flow metric Kanban teams optimize.
- WIP LimitA WIP (work-in-progress) limit is a cap on how many items may be active in a given workflow stage at once. By forcing a team to finish work before starting more, WIP limits expose bottlenecks, reduce context-switching, and shorten cycle time. They are the core mechanism that makes Kanban flow rather than pile up.
- Lead TimeLead time is the total elapsed time from when an issue is first created or requested to when it is delivered. Unlike cycle time, it includes the waiting period in the backlog before work begins. Lead time reflects the customer's experience of how long a request actually takes end to end.
- Cumulative Flow DiagramA cumulative flow diagram (CFD) is a stacked area chart showing how many items sit in each workflow state over time. The colored bands reveal flow health at a glance: a widening band means work is piling up in that stage, a steady set of parallel bands means smooth flow. It is Kanban's richest single picture of a system's behavior.