How does Kanban help identify bottlenecks in a process?

Kanban helps identify bottlenecks because it makes the process fully visual: every task and work stage is visible on the board, and any delay stands out immediately.

---

#Main mechanisms

1. Flow visualization All tasks are shown on the board in columns (To Do → In Progress → Done). If one of the columns starts to "swell up", that is where the process has slowed down.
2. WIP limits (Work In Progress) These limit the number of tasks being worked on at the same time. When the limit is exceeded, the team sees that the stage is overloaded and stops starting new tasks until the old ones are finished.
3. Time metrics (Cycle Time, Lead Time) These measure how many tasks "get stuck" at specific stages. An increase in cycle time at one stage points to a bottleneck.
4. Cumulative Flow Diagram (CFD) The chart shows where the number of unfinished tasks is growing. If one zone on the diagram is expanding, that is where the delay occurred.

---

#Conclusion

Kanban makes the flow of tasks transparent and measurable. It shows where the work slows down, both visually (on the board) and numerically (in the metrics), letting the team quickly remove bottlenecks and keep a stable rhythm.