Kanban: Limit Work in Progress, Flow Accelerates

A busy team is not necessarily a productive one. What most often stalls delivery in serious teams is not idleness but its opposite: starting too many things at once. Every item started and not finished holds effort and attention while delivering no value. Kanban addresses this by inverting the question: instead of "how do we finish more?" it asks "how do we start less?" In the Eighth Edition it is not a framework standing parallel to others but a visual workflow management method belonging to the family of flow-based scheduling.

Definition and Foundation

The Eighth Edition defines the Kanban method compactly: a visual workflow management method to limit work in process (WIP) based on lean principles, focusing on continuous delivery without overburdening the team. Four elements are needed to understand it:

• Flow-based scheduling — a project management approach focused on optimizing the flow of work through a system. One goal is to maximize the flow of deliverables based on resource capacity, materials, and other inputs; a related goal is to minimize time and resource waste and maximize the efficiency of processes and the throughput of deliverables. The guide notes that several adaptive methodologies use flow-based scheduling and often adopt these practices from flow-maximizing approaches.
• The Kanban board — a visualization tool that shows work in progress to help identify bottlenecks and overcommitments, thereby allowing the team to optimize the workflow.
• Theory of constraints — the guide pairs it with Kanban: a management philosophy focused on identifying and addressing the most significant limiting factor standing in the way of achieving a goal.
• Visual controls — in lean environments information radiators go by this name, illustrating processes so actual performance can easily be compared against expected.

A task board is broader than a Kanban board: a visual representation of planned work letting everyone see task status — work ready to start, work in progress, and work completed. It lets anyone see at a glance the status of a particular task or the number of tasks in each stage of work. Different color sticky notes can represent different types of work, and dots can show how many days a task has been in its current position.

Here comes the essential link: flow-based projects, such as those using Kanban boards, can use these charts to limit the amount of work in progress. And if a column is approaching the work-in-progress limit, team members can "swarm" around the current work to help those working on tasks that are slowing the flow.

How It Works in Practice

The WIP limit and swarming

The limit is not decoration on the board but the constraint the method works through. When a column fills, no new work is pulled into it, and the team shifts from starting more to finishing what is started. The guide names that behavior outright: swarming around the current work to help those on tasks that are slowing the flow. This inverts the common managerial instinct, which reads a full column as evidence of activity when in flow logic it is evidence of a bottleneck. The gap between the two readings is not philosophical: the first pushes toward adding resources, the second toward finishing what is started before starting more — two actions with opposite effects on delivery time.

Cycle time and lead time

The Eighth Edition distinguishes two measures on a Kanban board. Cycle time is the time from when a task starts until it is completed. Lead time is the time from when a task is put on the board until it is delivered. The difference is not a technicality: lead time includes the wait in the Ready column before work begins, and because the order of items in that column can be changed, lead time can be unpredictable. Improving cycle time alone therefore does not guarantee improving the experience of whoever is waiting for delivery.

Swappable items

The guide notes a property specific to the Ready column: tasks can be swapped with other tasks at any time. That is deliberate flexibility distinguishing a flow system from a timeboxed iteration — no prior commitment to the contents of a period, but an order adjustable right up to the moment of pull. The price is exactly what precedes: lead time's unpredictability. Promising a customer a delivery date on the basis of a stable cycle time promises what you do not control, because an item may wait in Ready for a period that shifts as the order shifts.

Kanban among scheduling approaches

The Eighth Edition names Kanban among scheduling approaches alongside the critical path method, the critical chain method, location-based scheduling, the Last Planner System, and Gantt charts. It also places it in the agile approaches figure beside Scrum, XP, Lean, and others. Kanban therefore reads in the guide as a scheduling approach and a flow management method, not an all-encompassing framework replacing project management. It can live inside a predictive project's changeable components, or carry the whole project where the work is inherently flow-shaped.

On the Exam

The 2026 ECO does not name Kanban in any enabler. The nearest tasks are Domain II Task 1, through "recommend a project management development approach (i.e., predictive, adaptive/agile, or hybrid management)"; Domain II Task 8, plan and manage schedule, through "prepare a schedule based on the selected development approach"; and Domain III Task 4, remove impediments and manage issues, through its enablers on evaluating the impact of impediments, prioritizing and highlighting them, and determining an intervention strategy to remove them.

The dominant pattern is a scenario describing a team delivering slowly and asking for the action. Four keys settle most of it:

• A full column with many items started and unfinished → lower the WIP limit rather than add effort.
• A question about surfacing bottlenecks → the board is defined as the tool for identifying bottlenecks and overcommitments.
• A stem mentioning the time from request to delivery → lead time, not cycle time.
• Work arriving with no steady rhythm → flow-based scheduling, not timeboxed iterations.

What deceives is options offering familiar management moves: adding people to the team, raising the WIP limit to absorb demand, or asking the team for overtime. All three treat the symptom rather than the cause; the second actually widens the bottleneck. So does conflating cycle time with lead time in a stem describing a customer complaining about a long wait — the complaint is about the second while the measure presented is usually the first.

Detailed Mistakes

A board with no WIP limit

The Eighth Edition's definition makes the limit a pillar rather than an option: a visual workflow management method to limit work in process. A board showing columns with no ceiling per column achieves the visual part and loses the part that changes behavior. The result is an attractive board displaying congestion instead of preventing it. The practical test is simple: if nothing stops you pulling a new item today, you do not have a limit.

Measuring productivity by items started

Flow-based scheduling states its goal as maximizing the flow of deliverables while minimizing time and resource waste. An item started and not delivered has produced no value yet, but it has consumed capacity and added context switching. Measuring activity by work started rewards precisely the behavior the method exists to restrain.

Ignoring the most significant limiting factor

The guide pairs Kanban with the theory of constraints: identifying and addressing the most significant limiting factor standing in the way of achieving a goal. Spreading improvement evenly across all stages wastes effort, because speeding up an unconstrained stage does not raise total throughput — the system moves at the pace of its slowest link, and improvement outside the constraint produces inventory in front of it rather than faster delivery.

Where It Does Not Apply

Kanban is an instrument of a flow-based system and presumes work that can be represented as successive stages every item passes through. Where the work is one large project with a single deliverable at the end — a predictive build phase where the cost of iterating far exceeds its value — flow offers nothing equivalent to what the critical path provides in sequencing dependencies and calculating float. Where a prior commitment to the contents of a period must be given to an external party, the "swap at any time" property collides with that commitment. One last note: the guide presents Kanban among scheduling approaches and among agile frameworks at once, so it is a tool that integrates with others rather than a comprehensive substitute — components with a high rate of change in a hybrid project may run on Kanban while the overall schedule stays planned with predictive techniques.