Flow Efficiency expresses the ratio of actual value-adding time to the total lead time of an item. If a feature spends ten days in the system but is actively worked on for only two of those days, the Flow Efficiency is 20 percent. The remaining 80 percent is wait time, for instance in queues before code review, testing, or deployment. This metric reveals where the greatest improvement leverage lies.
In practice, teams measure Flow Efficiency by logging for a set of items how long they are actively worked on versus how long they wait. Typical values in knowledge work range between five and 15 percent, which surprises many teams. The insight frequently leads to high-impact measures: smaller batch sizes, stricter WIP Limits, or introducing pair programming to eliminate review wait times. The point is not to work faster but to spend less time waiting.
Flow Efficiency comes from the Lean-Kanban environment and is one of the most informative metrics for the health of a work system. It should be observed as a trend over weeks, not as a single data point.
Apply methods, don't just know them. View trainings and workshops
