Kanban Explained: How a Simple Signal Tells Work When to Start
Kanban is one of those lean ideas that sounds almost too simple to matter, and that is exactly why it works. The word is Japanese for a card or visual signal. In a lean system, that signal does one job: it tells an upstream step to produce more only when a downstream step has actually consumed something. Nothing moves on a guess. After the supply disruptions still fresh in early 2021, the appeal of building only to real demand — rather than to an optimistic forecast — needs little explaining.
The contrast is between push and pull. In a push system, you make things according to a plan or forecast and hope demand shows up; unsold inventory and rush orders are the usual result. In a pull system, downstream consumption pulls replenishment through the process. Kanban is the mechanism that carries that pull signal.
How the signal travels
Picture a small stock of finished parts between two steps. Each container of parts carries a kanban card. When the next step takes a container to use it, the card comes off and goes back upstream. That returned card is the authorization to make exactly one more container — no card, no production. The number of cards in circulation is therefore a hard cap on how much inventory can ever exist between the two steps.
Consumption pulls the card. Work is used downstream, freeing a kanban that returns upstream as a signal.
The card authorizes replenishment. Upstream produces only the quantity the returned card represents — not a batch decided by a schedule.
Card count limits inventory. Because no work starts without a card, the total cards set a strict ceiling on work-in-process and stock.
Remove cards to expose problems. Deliberately reducing card count tightens the system and surfaces bottlenecks you would otherwise never see.
Kanban beyond the factory floor
The same logic runs a whiteboard of sticky notes for an office or software team. Columns represent stages of work; a limit on the number of items allowed in each column (a WIP limit) is the modern equivalent of a fixed number of cards. When a column is full, no new work may enter until something leaves. This is uncomfortable at first — people are used to starting tasks — but it is the point. Limiting work-in-process forces a team to finish before it starts, which shortens lead time and makes flow visible.
Start with how work flows today; map the columns honestly before adding limits.
Set WIP limits low enough to feel slight pressure, then adjust with evidence.
Treat a blocked, full column as a signal to help finish, not to start something else.
Make the board the single source of truth so the whole team sees the same flow.
A common mistake is treating kanban as just a pretty board. The board is only the visible part; the discipline is in honouring the limits and letting genuine demand — not habit or wishful planning — decide when work begins. Done that way, kanban quietly reduces inventory, exposes bottlenecks, and steadies a process without anyone having to predict the future.
If your operation is carrying too much work-in-process or reacting to forecasts instead of real demand, XNM's strategic advisory can help you design pull signals and limits that fit how your work actually flows.