Flow Efficiency
The ratio of active work time to total lead time, revealing how much time work items spend waiting versus being actively worked on.
Also known as: Process Efficiency, Flow Time Efficiency
Category: Software Development
Tags: lean, kanban, metrics, operations, agile, productivity
Explanation
Flow efficiency measures what percentage of an item's total lead time is spent in active work versus waiting in queues. It's calculated as:
**Flow Efficiency = (Active Work Time ÷ Total Lead Time) × 100%**
**Typical Values**:
| Context | Flow Efficiency |
|---------|----------------|
| Most organizations | 1–5% |
| Good performers | 15–25% |
| World-class | 40%+ |
| Theoretical maximum | ~85% (some wait is unavoidable) |
The fact that most organizations have flow efficiency below 5% is striking: for every hour of actual work, items sit idle for 19+ hours. A task with 8 hours of active work and a 4-week lead time has a flow efficiency of just 5%.
**Why It Matters**:
- **Reveals hidden waste**: Flow efficiency exposes the enormous amount of time items spend in queues, handoff buffers, and approval gates
- **Reframes improvement**: Instead of asking "how can we work faster?" (optimizing the 5%), teams ask "how can we reduce waiting?" (attacking the 95%)
- **Challenges assumptions**: Managers often focus on keeping people busy (resource efficiency), but this usually harms flow efficiency by creating queues
**Flow Efficiency vs. Resource Efficiency**:
This is a fundamental tension in process design:
- **Resource efficiency**: Maximize utilization of people/machines (keep everyone busy)
- **Flow efficiency**: Minimize the time items spend in the system (keep work moving)
You cannot maximize both simultaneously. High resource utilization creates queues (because when everyone is 100% busy, any new work must wait). These queues destroy flow efficiency. The sweet spot for most knowledge work is moderate resource utilization (70–80%) which allows good flow efficiency.
**How to Improve Flow Efficiency**:
1. **Reduce queue sizes**: Limit WIP at each stage so items don't pile up
2. **Eliminate handoffs**: Each handoff creates a queue. Cross-functional teams reduce handoffs
3. **Remove approval gates**: Replace sequential approvals with trust-based or automated checks
4. **Reduce batch sizes**: Smaller batches flow through faster with less waiting
5. **Visualize wait states**: Make queues explicit on your Kanban board (separate "waiting" from "working" columns)
6. **Address blockers immediately**: Don't let blocked items sit — escalate and resolve
**Measuring Flow Efficiency**:
To measure it, you need to track both:
- When work is actively being done (hands on keyboard, in discussion, etc.)
- When work is waiting (in a queue, waiting for review, blocked, etc.)
Some teams add "waiting" columns to their Kanban boards to make this visible. Others timestamp state transitions in their work tracking tools.
Related Concepts
← Back to all concepts