PRODUCTIVITYMonths to result

The Kanban Pull System

Let downstream demand control upstream production through visual signals

Problem it solves

low productivity

Best for

Operations teams managing multi-step processes with inventory between stages, supply chain managers, and any team that wants to replace forecast-driven scheduling with demand-driven flow.

Not ideal for

One-off project work with no repeatable processes; organizations with extreme demand variability that cannot be leveled; teams with no authority over their supply chain.

Overview

Why this framework exists

The Kanban Pull System is Toyota's method for controlling the flow of materials and information through a production process. A Kanban is a physical card or signal attached to each container of parts that authorizes the previous process to produce or deliver more. No Kanban means no production and no movement of goods.

The genius of Kanban is that it reverses the traditional push logic of manufacturing. Instead of each process producing as much as it can and pushing output downstream, each process only produces what the next process actually needs. This creates a chain reaction where real customer demand pulls through the entire system.

Kanban makes waste visible by design. When the system is functioning, excess inventory, overproduction, and waiting times become immediately apparent because they violate the Kanban rules. This visibility is what makes Kanban a powerful improvement tool, not just a scheduling mechanism.

Core principles

5 total
  1. Never produce or move anything without a Kanban authorization
  2. Defective products must not be accepted, produced, or sent forward
  3. Strictly follow the quantity specified on each Kanban card
  4. Always pull necessary items for the following process from the previous process
  5. Kanban is a tool for making waste visible, not an end in itself

Steps

5 steps
  1. Stabilize Your Processes First
    Before implementing Kanban, ensure your processes are stable and capable. You need reliable cycle times, consistent quality, and equipment that runs without frequent breakdowns. Without stability, Kanban will simply make chaos visible without providing a path to improvement.
    Pro tipEstablish standardized work for every process before introducing Kanban. This is your baseline for improvement.
    WarningAdopting Kanban without stable processes will lead to constant stockouts and finger-pointing rather than improvement.
  2. Define Kanban Types and Quantities
    Determine whether you need production Kanban (authorizing manufacturing), withdrawal Kanban (authorizing movement between processes), or both. Calculate the number of Kanban cards based on demand rate, lead time, container size, and a safety factor.
  3. Implement the Six Core Rules
    Train everyone on the Kanban rules: no defects passed forward, follow quantities exactly, always pull from previous process, produce only what Kanban specifies, produce in the order specified by the timeline, and tag a Kanban on each actual item. These rules are non-negotiable.
    Pro tipPost the rules visibly at every workstation. The rules are the system; without strict adherence, Kanban becomes just another piece of paper.
  4. Establish Heijunka for the Entire Line
    Level production across the whole production line so that Kanban can function smoothly. Unleveled demand causes upstream processes to oscillate wildly, defeating the purpose of pull. Mix different product types evenly throughout each production period.
    WarningWithout Heijunka, Kanban quantities will need constant adjustment and the system will feel chaotic.
  5. Continuously Reduce Kanban Cards
    Gradually reduce the number of Kanban cards in circulation. Each reduction lowers inventory and exposes the next layer of problems. When a problem surfaces, solve it permanently rather than adding cards back. This is how Kanban drives continuous improvement.
    Pro tipThink of Kanban cards as water level in a river. Lowering the water reveals the rocks (problems) underneath. Each rock you remove lets you safely lower the water further.

Checklist

Saved in your browser

Examples

2 cases
Supermarket Inspiration

Ohno observed that American supermarkets only restocked shelves when customers removed items, maintaining minimal but sufficient inventory. He realized this pull principle could replace the push scheduling common in factories, where each department produced as much as possible regardless of actual need.

OutcomeThis observation led to the creation of the Kanban card system, which became one of the most widely adopted production control methods in manufacturing history.
Sequential Parts Withdrawal

Toyota implemented stable Sequential Parts Withdrawal alongside Kanban to ensure that parts arrived at assembly lines in the exact sequence needed for mixed-model production. This eliminated the need for sorting and staging areas near the line.

OutcomeThe combination of Kanban and sequential withdrawal enabled Toyota to build multiple vehicle models on the same assembly line without the massive inventory buffers competitors required.

Common mistakes

3 traps
Treating Kanban as Just a Scheduling Tool
Many organizations implement Kanban for scheduling convenience but miss its deeper purpose as a waste-revealing mechanism. If you are not progressively reducing Kanban quantities and solving the problems that surface, you are not using Kanban as intended.
Ignoring the Prerequisite of Stability
Implementing Kanban on top of unstable, unpredictable processes creates more problems than it solves. The book emphasizes that Kanban requires stable standardized work, reliable equipment, and consistent quality as foundational prerequisites.
Blaming Kanban During Disruptions
When disruptions like natural disasters occur, critics often blame Kanban's low inventory philosophy. However, the system is designed to make the supply chain transparent and recoverable. High inventory obscures problems; low inventory with visibility enables faster recovery.

Origin story

How this framework came to be

Taiichi Ohno conceived the Kanban system after observing American supermarkets in the late 1940s and 1950s. He noticed that supermarket shelves were restocked only when items were taken by customers, creating a simple pull system. He adapted this concept to the factory floor, where production Kanban cards authorize manufacturing and withdrawal Kanban cards authorize movement of parts between processes.

The system was developed gradually within Toyota over many years. The book describes how Kanban rules were formalized and documented, including the critical rule that defective products must never be accepted, produced, or sent forward. Takeuchi emphasizes that maintaining the Kanban System requires tremendous ongoing effort and discipline.

Source

Traced to primary
Source · BOOK
The Toyota Production System Journey: The Continuously Changing Features of TPS and Lean Thinking
Noboru Takeuchi · 2022
Open source →

Related frameworks

Browse all Productivity →