Flow metrics measure how smoothly and quickly work moves through a workflow, especially in Kanban.
| Metric | Definition | Example |
|---|---|---|
| Lead time | Total time from when work is requested until it is delivered. | Request Monday, delivered Friday = 5 days |
| Cycle time | Time from when active work starts until it is completed. | Work starts Wednesday, done Friday = 3 days |
| Throughput | Number of work items completed in a period. | 12 tickets completed per week |
| Work in Progress (WIP) | Number of items currently being worked on. | 3 items in In Progress, 2 in Review |
| WIP age | How long an unfinished item has remained in progress. | One story has been open for 9 days |
| Blocked time | Time an item cannot move forward because of an impediment. | Waiting 3 days for API access |
| Queue time | Time an item waits before the next stage begins. | Story waits 4 days for code review |
| Flow efficiency | Percentage of total lead time spent actively working rather than waiting. | 2 active days out of 10 total days = 20% |
| Bottleneck | A workflow stage where work accumulates and slows delivery. | Review has 8 items while Done has only 1 |
Simple teaching explanation
Lead time measures customer waiting. Cycle time measures active workflow time. Throughput measures how many items are finished. WIP and queue measures show where work may be getting stuck.
Example workflow:
Requested → To Do → In Progress → Review → Done
- Lead time: Requested → Done
- Cycle time: In Progress → Done
- Throughput: Number moved to Done per week
- WIP: Number currently inside active workflow stages
The purpose of flow metrics is not to make people appear busy. It is to help the team reduce waiting, expose bottlenecks, and deliver value more predictably.
REF: AI Tools/ChatGPT as is
