Concept

What is Kanban

Kanban is a workflow management method that makes work visible and limits how much is done at once. The board is the visible part; the limit is the part that works.

Start freePricing

The word kanban comes from Japanese and literally means "card" or "visual signal". The concept was born in the Toyota Production System in the 1940s as a replenishment mechanism: a card signaled that a given part had been consumed and needed producing again. Nothing was produced without that signal.

In the 2000s, David J. Anderson adapted the idea to knowledge work, software, marketing, operations, in what is now called the Kanban Method. The essential change: instead of pulling part production, the team pulls tasks, and only when it has capacity for them.

  • Visualize the flow

    Columns represent stages of the real process, not the idealized one. Cards represent work items.

  • Limit work in progress

    Each column accepts a maximum number of items. It is the central rule, without it, the board is just a pretty list.

  • Manage the flow

    The focus is reducing the time between start and delivery, not increasing how many items were started.

  • Make policies explicit

    What "done" means has to be written down. An implicit criterion is a guaranteed source of rework.

What a WIP limit is and why it is the heart of the method

WIP stands for work in progress. The WIP limit defines how many items can be in each stage of the flow at the same time.

The intuition runs against common sense: limiting how much you start speeds up delivery. That happens because work stuck mid-flow generates no value at all, yet consumes attention, occupies context memory and ages, while the same effort concentrated on fewer items finishes sooner.

There is a mathematical relationship behind this, known as Little's Law: average lead time is proportional to the average amount of work in progress divided by the completion rate. Reducing WIP while holding capacity reduces lead time. It is not methodological opinion, it is queueing arithmetic.

Swimlanes: separating without fragmenting

Swimlanes are horizontal lanes cutting across the board's columns. They separate categories that share one flow but need to be read independently: different teams, different demand types, or an express lane for urgent items.

The most valuable use is usually an urgent-item lane with its own WIP limit, typically one. That gives the team a ready answer to "can we squeeze in one more urgent thing?": yes, when the lane is empty.

The same collection as a table, a board, a calendar and a gallery. Grouping by team or client is what produces swimlanes without splitting the board in two.

Kanban is not Scrum, and the difference matters

Scrum works in fixed-length iterations (sprints), with defined roles and scope committed per cycle. Kanban has no mandatory iteration, defines no roles and asks for no estimates: work flows continuously and is pulled as capacity allows.

That makes Kanban especially suited to teams whose demand arrives unpredictably, support, operations, on-demand marketing, platform teams. And it makes Scrum better suited when there is a scope worth protecting for a few weeks.

Worth noting that Kanban is a method of evolutionary change: it starts with the process you already have, without reorganizing job titles. That is precisely why it meets less resistance on adoption.

Calendar and timeline over the same collection. This is where Scrum's time box shows up, and it is exactly what Kanban does not require you to have.

The most common mistakes in practice

The first is adopting the board and ignoring the WIP limit. The result is a task list in columns, tidy, but with no effect whatsoever on delivery time.

The second is drawing the columns of the ideal process instead of the real one. If there is an informal "waiting on client" stage, it needs to be on the board; hiding it does not remove it, it only makes it invisible.

The third is treating the "done" column as a dead archive. Kanban lives on measuring the time between entry and exit, without that, the team loses the only indicator that would say whether the change it made improved anything.

Items completed per period and time spent in each stage. That is how a jammed column shows up as a number before the whole board seizes up.

Frequently asked questions

What is the difference between Kanban and Scrum?
Scrum organizes work into fixed-length sprints, with defined roles and scope committed per cycle. Kanban requires no iteration, roles or estimates: work flows continuously and is pulled as capacity allows, controlled by WIP limits. Kanban tends to serve better when demand is unpredictable; Scrum, when there is scope worth protecting for a few weeks.
What is the ideal WIP limit?
There is no universal number. A common heuristic is to start near the number of people in the stage and reduce it until the flow starts to stall, the point just before stalling is usually the useful limit. The sign that the limit is too high is many items started and few completed per week.
Does Kanban work for non-software teams?
It does, and that is one reason for its popularity. Marketing, legal, recruiting, support and operations use Kanban frequently, because the method assumes nothing about the kind of work, only that it moves through stages and that there is a limit to how much can be done at once.
Do I need a tool to apply Kanban?
No. Kanban works with sticky notes on a wall, and many teams start that way deliberately. A tool becomes worthwhile when the team is distributed, when cycle time needs measuring with some consistency, or when the board needs to talk to deadlines and metrics.

Keep reading

Apply Kanban with native WIP limits

In Workspacefy, WIP limits and swimlanes are part of the board, not an extension bolted on. Free to start.

Start free