lean-stack
Menu

Flow Efficiency Calculator

This flow efficiency calculator shows how much of a process's lead time is spent working on the item and how much is spent waiting. Enter the work time at each step and the wait that follows it, as you would read them off a value stream map.

Each step's work time and the wait before the next step

StepWorkWait after

Flow efficiency

3.9%

Work time
5.5 hours
Waiting
136 hours
Lead time
141.5 hours

Work is moving 3.9% of the time and waiting 96.1%. The longest wait is after Painting (48 hours). Halving it would cut lead time by 17.0%.

Your lead time as a timelineBars are drawn to scale. Green is work, gray is waiting.
Order entry
0.5 work · 16 wait
Cutting
1.5 work · 40 wait
Welding
2 work · 24 wait
Painting
1 work · 48 wait
Packing
0.5 work · 8 wait

On a value stream map this is the timeline ladder: waits on the upper rungs, work on the lower ones. The green slivers are the only time the item is being worked on.

Example values are filled in. Replace them with your own; nothing you type leaves your browser.

Worked example

The example values, step by step

  1. Step 1 · Work time

    0.5 + 1.5 + 2 + 1 + 0.5 hours

    = 5.5 hours

  2. Step 2 · Waiting time

    16 + 40 + 24 + 48 + 8 hours

    = 136 hours

  3. Step 3 · Lead time

    5.5 + 136 hours

    = 141.5 hours

  4. Step 4 · Flow efficiency

    5.5 ÷ 141.5

    = 3.9%

Reading the result

In the example, a welded frame spends 5.5 hours being worked on and 136 hours waiting between steps. For about 96% of its lead time, nothing is happening to it.

The longest queue is after painting, at 48 hours. Halving that one wait cuts lead time by 17%, more than making every work step twice as fast would.

What moves flow efficiency in the example
ChangeLead timeFlow efficiency
As is141.5 h3.9%
Halve the wait after painting117.5 h4.7%
Halve every wait73.5 h7.5%
Halve every work step instead138.75 h2.0%

Computed from the calculator's example values. Faster work steps shorten lead time a little but lower the ratio, because waits now take up a larger share.

Common data mistakes

  • Counting all work time as value-added. Inspection, rework and internal handoffs are work, but the customer would not pay for them.
  • Using planned or standard times instead of timing real items.
  • Leaving out the wait before the first step, such as an order sitting in an inbox.
  • Mixing units, such as minutes for work and days for waits, without converting.

The formula

How it's calculated

Lead time
Total work time + Total waiting time
Flow efficiency
Value-added (work) time ÷ Lead time × 100

Flow efficiency and resource efficiency

Resource efficiency asks how busy people and machines are. Flow efficiency asks how busy the item is. Keeping every resource busy tends to build queues, and queues lower flow efficiency.

Also called process cycle efficiency

In Lean Six Sigma the same ratio is often called process cycle efficiency (PCE). The formula is the same: value-added time divided by total lead time.

Measure the item, not the plan

Follow real items through the process and time them, or take dates from your workflow tool. Planned or standard times hide the waits you are trying to find.

Frequently asked questions

What is the formula to calculate flow efficiency?
Flow efficiency = value-added time ÷ total lead time × 100. Lead time is work time plus waiting time, measured from when the item enters the process to when it leaves.
Is flow efficiency the same as process cycle efficiency?
Yes, for practical purposes. Both divide value-added time by total lead time. Process cycle efficiency is the usual name in Lean Six Sigma, flow efficiency in lean and kanban.
How do you improve flow efficiency?
Reduce the waiting time rather than the work time. Limit work in progress, shrink batch sizes and attack the longest queue first. Making the work steps faster barely moves the ratio when waits dominate.
What is a good flow efficiency?
There is no universal target, because it depends on the process. Use it as a trend for your own process: track it after each change and look for waits to remove.
How is flow efficiency used in kanban for software teams?
Teams split board columns into active and waiting states, such as 'in progress' and 'ready for review'. Flow efficiency is the time in active columns divided by total time on the board.

Sources and further reading

For vendors

Built a lean tool?

Submit it for review. Every tool is checked against our listing criteria and researched from public sources. Approved tools join their category in the next published batch.