Kanban Board
Visualize your workflow and control how much work is in progress. A Kanban board makes flow, and its bottlenecks, visible, uses WIP limits to pull work through the system, and tracks lead and cycle time so you can improve throughput.
Open Kanban Board →What is a Kanban Board?
A Kanban board is a visual workflow tool that represents work as cards moving across columns that stand for the stages of a process, such as To Do, In Progress and Done. Kanban, Japanese for signboard, originated in the Toyota Production System as a signaling method for pull-based production.
Its defining practice is the work-in-progress (WIP) limit: a cap on how many items may occupy a stage at once. WIP limits are what turn a board from a simple task list into a flow-management system, because they force the team to finish work before starting more, exposing bottlenecks instead of hiding them behind piles of started-but-unfinished work.
By making flow visible and limiting WIP, Kanban implements a pull system: downstream capacity signals when upstream work should advance. Tracking lead time (request to delivery) and cycle time (start to finish of active work) then reveals where flow stalls and whether changes actually improve throughput.
In plain terms: A Kanban board shows every piece of work as a card moving left to right through your process. The trick that makes it powerful is limiting how many cards can sit in each column, which stops everyone from starting things and finishing nothing. Bottlenecks become obvious, and you fix flow instead of just staying busy.
Core Practices
Visualize Flow
Represent each work item as a card and each process stage as a column, so the whole flow and its blockages are visible at a glance.
Limit WIP
Cap the number of items allowed in each stage. This is the heart of Kanban: it forces finishing over starting and surfaces bottlenecks.
Manage Flow
Track lead and cycle time, watch where cards pile up, and improve the constrained stage to raise overall throughput.
Key Formulas
Using the Board to Improve Flow
Where cards accumulate in front of a stage, that stage is the bottleneck constraining the whole system. Little's Law makes the relationship concrete: for a given throughput, more work in progress means longer cycle times, so limiting WIP directly shortens delivery times.
Kanban improves evolutionarily, not by reorganizing everything at once. Start with the current process, make it visible, add WIP limits, and adjust them based on what the flow metrics reveal. Lowering a WIP limit often exposes the next constraint.
Assumptions & Validation
Visualized Real Process
The board reflects the actual workflow, not an idealized one.
If violated: Map the real stages, including queues and handoffs where work waits.
Enforced WIP Limits
WIP limits are actually respected, not routinely overridden.
If violated: Treat limit breaches as a signal to help finish work, not to raise the limit reflexively.
Flow Metrics Tracked
Lead and cycle time are measured to guide improvement.
If violated: Record timestamps as cards move so metrics are available.
⚠️ Check assumptions first
A Kanban board without enforced WIP limits is just a task list, and delivers almost none of the benefit. The discipline of finishing work before starting new work is what exposes bottlenecks and shortens cycle time. When a WIP limit is hit, the correct response is usually to swarm on finishing the constrained work, not to raise the limit, which simply restores the pile-up the limit was meant to prevent.
When NOT to Use Kanban Board
Fixed-Scope Time-Boxed Work
For work best planned in fixed iterations with committed scope, a Scrum or sprint approach may suit better than continuous flow.
Purely Sequential One-Off Projects
For a single linear project with hard dependencies, a Gantt chart shows the schedule more clearly.
No Repeatable Workflow
If there is no recurring process to visualize, Kanban has little to manage.
Industry Applications
Production Flow
Signal pull-based replenishment and material movement on the shop floor, Kanban's original use.
Improvement Backlogs
Manage a queue of improvement actions or Kaizen tasks with visible ownership and WIP limits.
Service & Office Work
Visualize and improve the flow of tickets, requests or cases in knowledge and service work.
Maintenance & Support
Track work orders through stages and expose where jobs stall.
Frequently Asked Questions
What is a work-in-progress (WIP) limit and why does it matter?
A WIP limit caps how many work items may occupy a stage of the board at once. It matters because it forces the team to finish work before starting more, which exposes bottlenecks instead of hiding them behind piles of unfinished work. WIP limits are what turn a Kanban board from a simple task list into a genuine flow-management system, and they are the practice most responsible for Kanban's benefits.
What is the difference between lead time and cycle time?
Lead time is measured from when a request is made to when it is delivered, capturing the customer's full waiting experience including time in queues. Cycle time is measured from when active work begins to when it is completed, capturing how long the work itself takes. Lead time is always at least as long as cycle time, and comparing the two reveals how much time items spend waiting.
What is Little's Law and how does it apply to Kanban?
Little's Law states that the average work in progress equals throughput multiplied by average cycle time. In Kanban terms, for a given delivery rate, more work in progress means longer cycle times. This is the mathematical reason WIP limits work: capping the number of items in progress directly shortens how long each item takes to move through the system.
How is Kanban different from Scrum?
Scrum organizes work into fixed-length iterations, or sprints, with a committed scope and defined roles and ceremonies. Kanban manages a continuous flow of work with no fixed iterations, using WIP limits and flow metrics, and it does not prescribe roles. Kanban can be applied to an existing process evolutionarily, while Scrum imposes a more defined structure; teams sometimes combine elements of both.
What does it mean when cards pile up in one column?
An accumulation of cards in front of a stage indicates that stage is a bottleneck constraining the whole flow. The pile-up shows that upstream stages are producing work faster than the bottleneck can process it. The Kanban response is to focus improvement and, where possible, capacity on that constrained stage, because raising the throughput of the bottleneck raises the throughput of the entire system.
Do I have to change my process to start using Kanban?
No. One of Kanban's principles is to start with your current process and workflow as they are, visualize them, and then improve evolutionarily. You begin by mapping the real stages and adding WIP limits, then adjust based on what the flow metrics reveal. This gradual approach makes Kanban low-risk to adopt compared with methods that require an immediate structural change.
Make Flow Visible and Limit WIP
Visualize workflow, cap work in progress, and shorten cycle time. Free during Beta.
Open Kanban Board →