Kanban Board

A kanban board is a way of making work visible by laying it out as columns and cards. Each column is a stage in the workflow — a simple board might read Backlog, In Progress, and Done, while a fuller one adds Ready, In Review, and Testing. Each card is a single unit of work, such as a task, a feature, or a support ticket, and it moves rightward across the columns as it progresses. The team pulls a card into the next stage only when there is capacity to work on it, rather than having work pushed onto it. The board can be a physical wall of sticky notes or a digital tool such as Trello or a Jira board, but the idea is the same — show the whole flow of work at a glance.

The feature that turns a plain board into a genuine kanban system is the work-in-progress limit, a cap on how many cards a column may hold at once. If the In Progress column is limited to five cards, no one starts a sixth until one finishes. That constraint sounds restrictive, but it is the point. It stops the team from juggling too many half-done things, and it makes trouble visible: when cards pile up in front of a stage, that stage is the bottleneck. Kanban grew out of the Toyota Production System, where physical cards signaled when to replenish parts, and the software version keeps the same spirit of pulling work through a system at a sustainable pace.

A kanban board is easy to confuse with a Scrum board, since both use columns and cards, but they run on different rhythms. A Scrum board is tied to a sprint — a fixed time box, often two weeks. The team commits to a set of work at the start, the board tracks that batch, and at the sprint's end the board is cleared and the cycle restarts. A kanban board has no sprints and no reset. Work flows continuously, cards enter whenever priorities demand, and there is no fixed batch to finish by a deadline. Scrum plans in iterations, while kanban manages a steady stream that never stops to regroup.

The other big difference is where each method puts its limits. Scrum limits work indirectly, by fixing how much the team pulls into a sprint. Kanban limits work directly and continuously, through work-in-progress caps on the columns themselves, so the constraint applies all the time rather than once per sprint. That makes kanban a strong fit for teams with unpredictable, incoming work — support desks, operations, maintenance, or a marketing team fielding steady requests — where committing to a two-week batch would be artificial. Scrum suits teams that can plan in chunks and want the cadence of regular sprint reviews. Many teams blend the two into Scrumban, borrowing kanban's flow and limits inside a Scrum shell.

Get value from a kanban board by first mapping the columns to how work actually moves, not to an idealized process. If cards really pass through a review step and a testing step, give those stages their own columns, because a board that hides real stages hides real delays. Then set work-in-progress limits and hold to them, since a board without limits is just a decorated to-do list. Watch where cards accumulate and treat that column as the constraint to fix, whether that means adding help, breaking work down, or clearing a dependency. Track how long cards take to cross the board, so you can see whether flow is improving rather than guessing.

The failures are predictable. Teams often skip work-in-progress limits, so everything is in progress and nothing finishes. Some let columns drift out of step with reality, so the board flatters the process instead of describing it. Others use the board only as a status display for managers and never act on the bottlenecks it reveals, which wastes its main gift. A kanban board earns its keep when the team treats the pile-ups as signals — pausing new work to unblock the stuck stage — rather than starting yet another card. Kept honest and limited, the board holds a team's attention on finishing work, not merely on starting it. Teams that absorb that shift stop judging themselves by how busy the board looks and start judging themselves by how much actually ships.

A kanban board comes from the Japanese kanban, meaning signboard, used in the Toyota Production System, and it visualizes work as cards moving through columns with work-in-progress limits that expose bottlenecks.

Etymology: source.

Search interest for this term over the last five years:

View interest-over-time on Google Trends →

Areas of marketing where kanban board is a core concern: