Suggest an edit

Improve this article

Refine the answer for “What metrics are used in Kanban?”. Your changes go to moderation before they’re published.

Approval required

Content

What you’re changing

Title (EN)

Short answer (EN)

Shown above the full answer for quick recall.

Answer (EN)

In Kanban, metrics are needed for **analyzing the stability of the flow** and continuously improving the process.
They help measure the speed, quality, and predictability of the team's work.

---

### Main Kanban metrics

1. **Cycle Time**
Shows how much time a task spends in active work - from "In Progress" to "Done".
The smaller and more stable the cycle time, the more predictable the process.
2. **Lead Time**
Measures the full time - from when a task appears to when it is completed.
Important for assessing how long the customer actually waits for the result.
3. **Throughput**
The number of tasks completed over a given period (for example, per week).
Helps understand how much work the team can consistently handle.
4. **WIP (Work In Progress)**
The number of tasks in progress at the same time.
Controlling and limiting WIP prevents overload and keeps the flow smooth.
5. **Cumulative Flow Diagram (CFD)**
Visualizes how tasks move through the stages of the process and shows bottlenecks.
6. **Flow Efficiency**
The percentage of time a task is actually being worked on, rather than waiting.
Calculated as:
[
\text{Flow Efficiency} = \frac{\text{active work time}}{\text{total lead time}} \times 100%
]

---

### Conclusion

Kanban metrics give a quantitative picture of the flow: **speed (throughput), time (cycle/lead time), load (WIP), and efficiency (flow efficiency)**.
Analyzing them together keeps the process **transparent, stable, and manageable**.

Markdown · drag & drop images · ⌘B / ⌘I shortcuts229 words

For the reviewer

Note to the moderator (optional)

Visible only to the moderator. Helps review go faster.