Kanban
- Introduced by
- Taiichi Ohno
- Year
- 1950
- Type
- Production control system
- Family
- Lean Manufacturing
What does it do?
Kanban is a pull-based production control system developed by Taiichi Ohno at Toyota in the 1950s that uses visual signals (traditionally cards or bins) to trigger production and movement of materials based on actual demand rather than forecasts.
The Japanese word 'kanban' means 'visual card' or 'sign,' and the system operates on the principle that work should flow in response to downstream requirements. Kanban is a foundational element of the Toyota Production System and lean manufacturing, enabling just-in-time production, reduced inventory, and improved flow efficiency.
The intuition behind the method
Traditional manufacturing pushes inventory through the system based on forecasts—if you predict demand for 100 units, you produce 100, even if only 80 sell. Kanban inverts this logic. Imagine a card that says 'make more' sitting on top of a bin of finished goods. When a customer takes a unit, a worker removes the card, signals the production line, and produces only one replacement unit. Each process step is triggered only when the downstream step needs material. The system creates a visual chain of signals flowing backward through the production line, ensuring that work-in-process inventory never exceeds the capacity limit (the number of kanban cards). The result: smoother flow, less waste, and faster response to actual demand changes.
History
Taiichi Ohno developed kanban at Toyota in the early 1950s as a way to implement just-in-time manufacturing in a complex, multi-product environment. The system evolved alongside other Toyota Production System practices (standardized work, visual management, continuous improvement) and became a cornerstone of lean manufacturing globally. Initially physical cards or bins, kanban has evolved to include digital signals and software systems. Today, kanban principles are applied far beyond manufacturing—in software development (Kanban boards for task management), healthcare (patient flow), and service industries.
When to use it
Kanban is ideal for repetitive manufacturing with relatively stable demand and short lead times. Apply it in plants producing multiple SKUs on the same equipment, in supply chains with predictable demand patterns, or in service environments with variable workload (e.g., IT support tickets, hospital patient flow). Less effective in high-variety, low-volume job shops or in processes with very long, variable lead times. Best results emerge when combined with standardized work, SMED, and TPM.
Limitations and considerations
- Requires stable demand and short, predictable lead times; highly seasonal or erratic demand can cause stock-outs or excess inventory
- Setting optimal kanban card counts requires experimentation; too few cards cause stock-outs, too many defeat the inventory reduction purpose
- Works best in relatively simple, linear supply chains; complex, multi-product networks may require more sophisticated planning
- Relies on disciplined adherence to kanban rules; any deviation (emergency production, hoarding) undermines effectiveness
Source conditions do not replace independent scientific review or validation by an analysis engine.
Strengths
- Dramatically reduces work-in-process inventory (often by 30–50 percent) and frees up cash
- Improves flow efficiency and shortens production lead times through visual signal discipline
- Enables faster response to demand changes; if demand drops, the production rate adjusts immediately as kanban signal frequency decreases
- Makes problems visible; when a kanban signal is delayed, the bottleneck is obvious and can be addressed
- Simple to understand and implement; no complex software required (though digital kanban tools exist)
Applications
- A large automotive OEM uses kanban to manage material flow between assembly lines, reducing work-in-process inventory by 40 percent and improving equipment uptime through reduced congestion
- A medical device manufacturer implements two-bin kanban for 500+ component types, improving inventory turns from 8 to 18 annually while maintaining 99.5 percent on-time delivery
- An electronics assembly contract manufacturer uses digital kanban to synchronize multiple production lines feeding a final assembly operation, reducing lead time from 21 days to 8 days
- A hospital implements kanban for surgical supply management, reducing stock-outs by 30 percent and lowering supply room inventory costs by 25 percent through visual demand-driven replenishment
How it works
How it works
Map the value stream and identify key work stations or inventory points where kanban signals will control material flow.
Set the number of kanban cards (and thus the maximum work-in-process inventory) for each station based on lead time and demand variability.
When downstream demand consumes material, a kanban card is returned to the upstream process, signaling a production or replenishment order.
Upstream processes produce or supply material only in response to kanban signals, never ahead of downstream demand.
Monitor kanban board metrics (cycle time, inventory turns, signal response time) and adjust card counts to optimize flow and balance capacity.
Common pitfalls
- Setting kanban limits too high as a buffer against uncertainty, negating the inventory reduction benefit
- Implementing kanban without addressing root causes of variability (forecast errors, long lead times, quality issues), leading to frequent stock-outs
- Treating kanban as a card system only, without the supporting lean practices (standardized work, SMED, TPM) that make it effective
Frequently asked questions
How many kanban cards should we have?
A common formula is: (Average demand per day × Lead time in days) + Safety stock. Start conservative (higher count), measure actual flow, and gradually reduce the count while monitoring for stock-outs. The goal is the minimum card count that maintains service level.
What if demand is highly seasonal?
Kanban works best with stable demand. For seasonal products, you can use different card counts for peak vs. low seasons, or use a hybrid approach: kanban for base load demand and forecasting for seasonal spikes. Consider reducing lead times to enable faster response to demand shifts.
Can we use digital kanban instead of physical cards?
Yes. Digital kanban systems (web-based or IoT-enabled) offer benefits like real-time visibility and automatic ordering. However, the principle remains the same: visual signals triggering pull production. Physical cards are easier to start with and are actually more resilient to system outages.
Does kanban work for services (e.g., software teams, customer support)?
Absolutely. Kanban boards are widely used in software development to limit work-in-progress and improve flow. The same principles apply: visualize work, limit WIP, respond to pull signals (customer requests), and measure cycle time. Services benefit especially from the visibility and flow efficiency gains.
Related methods
Sources
Ohno, T. (1988). Toyota production system: Beyond large-scale production. Cambridge, MA: Productivity Press.
Open publication referenceCopied.Rother, M., & Shook, J. (2003). Learning to see: Value stream mapping to add value and eliminate muda. Cambridge, MA: Lean Enterprise Institute.
Open publication referenceCopied.