What Is a Kanban Board? How to Use It to Manage Product Work
A Kanban board is a visual workflow management tool that displays work as cards moving through defined stages — from initial request to completion. Each column represents a stage in the work process; each card represents a unit of work. By making the status of all work visible simultaneously, a Kanban board helps teams manage their workflow, identify bottlenecks, limit work in progress, and maintain a smooth, predictable flow of delivery.
Kanban originated in Toyota’s manufacturing system as a method for controlling inventory and production flow. It was adapted for software development by David Anderson in the mid-2000s and has since become one of the most widely used agile workflow management approaches.
The Core Elements of a Kanban Board
Columns (Stages)
Each column represents a stage in the team’s workflow. Common columns include:
- Backlog — Work that has been identified but not yet started
- Ready/Selected — Items prioritized and ready to begin
- In Progress — Work actively being worked on
- In Review — Work completed and awaiting review (code review, design review, QA)
- Done — Completed and accepted work
Teams customize their columns to reflect their actual workflow stages, not an idealized version.
Cards (Work Items)
Each card represents a unit of work — a user story, bug fix, task, or feature. Cards typically display the work item title, assignee, priority, and any relevant labels or metadata.
WIP Limits (Work in Progress Limits)
WIP limits are maximum numbers of cards allowed in a column at any given time. When a column is at its limit, no new work can enter until an existing item moves forward. WIP limits prevent teams from accumulating large queues of in-progress work that slows delivery and obscures bottlenecks.
Swimlanes
Horizontal rows within the board that create sub-categories — by team, work type, priority level, or customer. Swimlanes add another dimension of organization without eliminating the column-based flow view.
How Kanban Differs from Scrum
| Kanban | Scrum | |
|---|---|---|
| Iteration | Continuous flow, no fixed sprints | Fixed-length sprints |
| Planning | Continuous, just-in-time | Sprint-based, time-boxed |
| Roles | No prescribed roles | Product Owner, Scrum Master, Dev Team |
| Commitment | No sprint commitment | Sprint commitment |
| Best for | Variable, continuous work | Feature development with batched planning |
Kanban and Scrum are not mutually exclusive. Many teams use “Scrumban” — combining Scrum’s planning and retrospective structure with Kanban’s visual management and WIP limits.
Using WIP Limits Effectively
WIP limits are one of the most counterintuitive and impactful elements of Kanban. Restricting how much work can be in progress at once seems like it would slow things down — in practice, it speeds things up.
When WIP is limited:
- Bottlenecks become immediately visible (a blocked column is full; upstream columns are empty)
- Team members are motivated to help finish in-progress work rather than starting new items
- Context-switching decreases as individuals focus on fewer items
- Cycle time (the time from starting a card to completing it) shortens
Finding the right WIP limits requires experimentation — start with rough estimates and adjust based on observed flow.
Kanban Metrics
Lead Time
The total time from when a card is created (or a request is made) to when it is completed. Lead time reflects the full customer experience of how long it takes for a request to be delivered.
Cycle Time
The time from when work actively begins (card moves to “In Progress”) to when it is completed. Cycle time reflects the team’s internal delivery speed.
Throughput
The number of items completed per time period. Throughput is the most direct measure of team delivery capacity.
Cumulative Flow Diagram
A visualization of how cards accumulate in each stage over time. A healthy cumulative flow diagram shows bands of roughly consistent width; widening bands indicate accumulating work in a stage and signal bottlenecks.
Key Takeaways
A Kanban board is one of the simplest and most effective tools for managing product and development workflow. By making work visible, applying WIP limits to prevent overloading, and creating clear flow through defined stages, it gives teams a shared, real-time view of their delivery capacity and helps them identify and address bottlenecks before they compound. The best Kanban boards are simple, maintained by the whole team, and evolved continuously as the team’s workflow understanding improves.