Home › The Garage › Kanban & pull
Lean

Kanban & pull systems

A pull system starts work only when there is capacity to finish it. Kanban makes that visible — and the moment you cap work in progress, the hidden queues and bottlenecks come into the open.

By LeanBean · Updated November 2026 · 5 min read
What's in this guide
  1. Push vs pull
  2. Why limiting WIP works
  3. The Kanban board
  4. How to start
  5. Common questions
To do DoingWIP limit: 2 Done “Doing” is capped at two. Nothing new starts until something finishes and moves to Done.
The WIP limit on “Doing” is the whole trick: it forces finishing over starting.

Push vs pull

In a push system, work is handed on as soon as it is ready, whether or not the next step can take it — so queues build up between stages. In a pull system, a stage takes new work only when it has finished its current work and has capacity. Kanban (literally “signal card”) is the mechanism: a visible signal that says “I’m ready for the next item,” so work is pulled through rather than pushed in.

Why limiting WIP works

The core move is a work-in-progress (WIP) limit: a cap on how many items can be in a stage at once. It feels counter-intuitive — surely more in flight means more done? But starting everything means finishing nothing: items sit half-done, context-switching multiplies, and queues hide the bottleneck. Cap the WIP and the team is forced to finish before starting, lead times fall, and the flow efficiency of the whole system rises.

The Kanban board

A board makes the system visible: columns for each stage, a card per item, and a WIP limit written on the columns that need one. When a column is full, that is a signal — not to push harder, but to help clear the blockage downstream. The board turns an invisible flow of work into something a team can see and manage together.

How to start

Start with the work you already do
You don’t redesign anything to begin. Map your current stages into columns, put today’s real work on cards, and watch where they pile up — that pile is your bottleneck. Add a WIP limit there first. Kanban is an evolutionary method: it improves the process you have rather than replacing it, which is why it meets so little resistance.

Describe a process. Get the whole analysis.

LeanBean turns a plain-language description of any process into a professional map — with Lean waste, SIPOC, design-thinking, AI-readiness and capacity analysis built in, and a Transformation Coach that sequences the fixes. Free to start.

Build your first map free →

The Garage — a community of practice

The Garage is where Lean, process and AI-readiness practitioners learn in the open — short lessons, real examples, and a place to compare notes. Join the community: follow along, try it on your own work, and share what you find.

Common questions

What is a pull system?

A way of organising work where a stage takes on new work only when it has capacity to finish it, rather than having work pushed onto it. This keeps queues small and makes bottlenecks visible instead of hidden in a backlog.

What does a WIP limit do?

A work-in-progress limit caps how many items a stage can handle at once. It forces the team to finish work before starting more, which cuts context-switching, shortens lead times and exposes where the flow is actually constrained.

Is Kanban the same as Scrum?

No. Scrum organises work into fixed-length sprints with set roles and ceremonies. Kanban has no sprints or prescribed roles — it visualises a continuous flow and limits work in progress. Many teams blend the two.

Where did Kanban come from?

It began as a signalling method on lean manufacturing lines to pull parts only as they were needed, and was later adapted for knowledge and software work. The principle — pull, don’t push, and limit work in progress — carries across both.

Related guides: Process cycle efficiency · Value stream mapping · Scrum & Kanban for delivery