Flow Efficiency Calculator
See how much of your delivery clock is real work versus waiting - and why killing queue time beats coding faster.
Work items (hours)
Editable estimates. Enter active (working) and wait (idle/queue) hours for a typical item.
Flow efficiency
Typical range (most teams sit at 15-25%)
- Active (working) 8h (17.4%)
- Wait (idle / queue) 38h (82.6%)
Cutting queue time usually moves the number more than pushing people to code faster - because the wait is the bigger slice.
How to read your flow efficiency
Flow efficiency answers a blunt question: of all the time a work item was alive, how much was it actually being worked on? The rest is wait time - sitting in review queues, blocked on approvals, waiting for a dependency, or parked in a "done, awaiting deploy" limbo. Most teams are surprised to find they sit at 15-25%, meaning three to five hours out of every four are pure waiting.
That reframes where to spend effort. When most of the clock is queue time, asking engineers to code faster barely moves the outcome - you are optimizing the small slice. Cutting wait attacks the big slice: smaller batches, faster reviews, fewer handoffs. See how this connects to cycle time, lead time for changes, and DORA metrics.
Estimates are a fine start, but the real win is measuring active versus wait time from your actual workflow rather than guessing. Explore how FeatureFactory helps you measure delivery, or try a related cycle time calculator.
Frequently asked questions
Measure the wait - don't guess at it
FeatureFactory tracks real active and wait time across your workflow, so you can plan, build, and measure your way to higher flow efficiency instead of estimating it.
Get early access