What Is Kanban?

Kanban is a visual workflow management method that uses columns and cards to represent work items moving through defined stages. Originally developed in manufacturing, Kanban has been widely adopted by software and product teams as an alternative or complement to Scrum. Its core principles are visualizing work, limiting work in progress (WIP), and optimizing flow.

Why Kanban matters

Kanban makes work visible. When every task is a card on a board, the team can see at a glance what is in progress, what is blocked, and where bottlenecks are forming. This visibility is the foundation for improving flow. Without it, teams rely on status meetings and manual check-ins to understand what is happening, which is slower and less reliable.

The WIP limit is what distinguishes Kanban from simply using a task board. By limiting how many items can be in any single stage at once, teams avoid the trap of starting everything and finishing nothing. WIP limits force the team to finish current work before pulling new work, which reduces context switching and improves completion rates.

How Kanban works

A Kanban board has columns that represent stages of your workflow. A simple board might have three columns: To Do, In Progress, and Done. More detailed boards add columns like Backlog, Ready for Review, Testing, and Deployed. Each work item is a card that moves from left to right as it progresses through stages.

Each column has a WIP limit: the maximum number of cards it can hold at any time. When a column is at its limit, no new cards can enter until an existing card moves to the next stage. This creates a pull system: work is pulled forward when capacity is available, rather than pushed in regardless of capacity.

Teams track two key metrics: lead time (how long a card takes from entry to completion) and throughput (how many cards are completed per time period). Improving these metrics over time is the measure of success in Kanban.

Common mistakes

• Using a Kanban board without WIP limits, which is just a task list with columns.
• Setting WIP limits but ignoring them when things get busy.
• Not tracking flow metrics (lead time, throughput), so there is no way to know if the process is improving.
• Having too many columns, which creates unnecessary handoff points and slows flow.

Related terms

• Scrum

  The sprint-based alternative to Kanban's continuous flow

• Agile

  The broader methodology family that includes Kanban

• Velocity

  The sprint-based metric; Kanban uses throughput and lead time instead