Kanban: Limit Work in Progress, Flow Accelerates
Starting many items at once slows flow, not speeds it.
- To do — Ordered work not yet started
- In progress — Work in progress at a maximum
- Done — Completed work
- WIP limit — A cap that prevents congestion
Kanban is an agile method that makes work visible on a board of columns representing its stages, from to do, to in progress, to done. It limits work in progress at each stage to reduce distraction and speed flow. It is a pull system: new work starts when capacity is available, not when pushed. By monitoring flow and cycle time, bottlenecks are revealed and continuously improved.
Starting many items at once thinking it is productivity. Exceeding the WIP limit slows flow and lengthens cycle time.
Limit work in progress, and cycle time shortens as flow accelerates.
Ready to start serious PMP prep?
Subscribe now →Read the details
Kanban is a flow management method focused on smooth work flow more than committing to fixed iterations. It starts by making work visible on a board whose columns are workflow stages, so everyone sees where each item stands. Then it imposes a work-in-progress limit at each stage, the core of the method: limiting what is done at once prevents congestion, reveals bottlenecks, and shortens cycle time. It is a pull, not push, system: new work starts only when capacity frees, pulling from the previous stage. By measuring flow metrics such as cycle time and throughput, the team continuously improves its flow rather than merely adding effort.
Frequently asked questions
What is Kanban?
An agile method making work visible on a board and limiting work in progress to speed flow.
What is a WIP limit?
A cap on the number of items in progress at once, preventing congestion.
Why does much simultaneous work slow flow?
Because it increases distraction and context switching and lengthens cycle time.
What is a pull system?
Starting new work when capacity is available, rather than pushing it to the team.
What is the difference between Kanban and Scrum?
Kanban focuses on continuous flow and WIP limits; Scrum on fixed iterations and defined roles.