What Is Kanban? Meaning, Boards, and How It Works

What Is Kanban? 

Kanban is a visual system for managing work and inventory as it moves through a process. Each work item or batch of parts becomes a card on a board, and a downstream step signals for more only when the line is ready to take it. Production follows real demand instead of a forecast.

That focus on real demand pays off because inventory is costly to hold. Industry benchmarks put the yearly cost — capital, storage, insurance, and obsolescence — at 20% to 30% of total inventory value. US manufacturers carry about 1.5 months of sales as inventory at any given time, so keeping stock lower without causing shortages saves real money.

{{callout1}}

How Does a Kanban System Work?

A Kanban system has three parts: a board that makes the work visible, a pull signal that controls when new work starts, and a limit on how much can be in progress at once.

• The board: Divide the process into columns. For office work, the column headers might be To Do, In Progress, and Done; on a line, it’s the actual production stages. Create a card for each task or batch of parts used in the process. The cards move across the columns as the work advances, so anyone can see the work's status at a glance.
• The pull signal: Work advances only when the next step asks for it (i.e., when a card moves across the board). A card passed back to the start is the signal to make or replenish more. Nothing gets produced until something downstream is used up — the basis of just-in-time production.
• WIP limits: Each column caps the number of cards it can hold. This is called the WIP limit. When a column hits that cap, the step feeding it pauses to clear the backlog versus piling on more. This also surfaces exactly where work gets stuck. There's math behind this: Little's Law, formulated by MIT's John Little in 1961, holds that cycle time equals work in progress divided by throughput. So at a steady work rate, less WIP means each item finishes sooner.
  Cycle time = WIP / Throughput

This is the opposite of a push system, where each station works to a schedule and hands materials off to the next station — whether or not it is ready, and piling up unfinished work if it isn't. Kanban replaces the schedule with a signal, so work moves forward only when there's capacity for it.

Kanban on the Manufacturing Floor

Kanban started on the shop floor, and physical signals still run material flow in many plants. There's a lot of capital at stake: US manufacturing and trade inventories totaled about $2.7 billion in early 2026. Pull systems like Kanban keep that number down. 

A physical Kanban system swaps the board format for Kanban cards that travel with containers of parts. When the parts are used, the card goes back upstream to authorize making or moving more.

• Production Kanban: Authorizes a workstation to produce a specific quantity of a part.
• Withdrawal (move) Kanban: Authorizes moving parts from one stage or storage point to the next.

The two-bin system is the simplest form. One bin of parts sits at the workstation while a second waits in reserve. When the first empties, that empty bin becomes the reorder signal and the operator switches to the reserve. As long as a bin lasts longer than the time to replenish it, the station never runs dry. This system works best for small, high-use items, and pairs naturally with kitting.

Electronic Kanban (e-Kanban) swaps physical cards for barcode scans, software triggers, or sensors that fire the same pull signal automatically. It can even extend to suppliers in real time to order the right amount of raw materials, preventing stockouts.

{{callout2}}

Kanban vs. Scrum

Kanban and Scrum both manage work in progress, but they run on different clocks — Scrum in fixed-length sprints with set roles and a locked scope, Kanban as a continuous flow that lets priorities change whenever the next card is pulled.

Kanban Pros and Cons

Benefits of Kanban

• Less waste: Pull production makes only what the next step consumes, so overproduction and excess inventory have nowhere to hide.
• Visibility: The board and its WIP limits expose bottlenecks early, which supports fast root cause analysis.
• Flexibility: Teams reprioritize between cards without disrupting a fixed plan.
• Continuous improvement: The system is built to be tuned — tighten a WIP limit, adjust card counts, and measure the result.

Limitations of Kanban

• Weak on fixed deadlines: With no sprints or due dates built in, teams that need firm delivery commitments have to add that structure themselves.
• Sizing has to be right: Card and bin quantities have to match real demand and lead time. Set them wrong, and you get stockouts or excess inventory.
• It depends on discipline: Boards reflect reality only if the team keeps them current. Stale cards break the signal.
• It won't fix upstream problems: Kanban controls flow, not equipment reliability. If breakdowns drive your losses, pair Kanban with maintenance and overall equipment effectiveness (OEE) tracking.

How To Implement Kanban in 5 Steps

1. Map the current workflow: Document the real stages a part or task passes through, with the operators who run them (not the version on the org chart). A value stream map is a strong starting point.
2. Build the board: Create a column for each stage and a card for each item so that the whole flow is visible to every shift.
3. Set WIP limits: Cap each column based on real capacity. The limits will feel tight at first — that's the point; they force finishing over starting.
4. Define the pull signals: Decide what triggers replenishment — a returned card, an empty bin, a scan — and match card or bin quantities to demand and lead time.
5. Review and improve: Hold regular check-ins, treat a blocked column as a signal, and adjust limits and quantities as conditions change.

The Bottom Line

Kanban works because it ties production to what's actually being used, not to a schedule set weeks ago. When the work is visible and the amount in progress is capped, the problems that usually stay hidden — excess inventory, a station quietly falling behind — show up early enough to fix.

It only holds if the people running the line own the board and adjust the limits as the work changes; left alone, it slips back to the old way within a couple of months. See how Redzone's Productivity software gives frontline teams real-time visibility into flow and bottlenecks on every line.