Kanban
Also known as: visual management, pull system
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.
Key highlights
- 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)
Intuition
This section is available to Pro members. Upgrade to Pro
How it works
This section is available to Pro members. Upgrade to Pro
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.
Strengths & limitations
- 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)
- 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
Common pitfalls
This section is available to Pro members. Upgrade to Pro
Applications
This section is available to Pro members. Upgrade to Pro
Frequently asked
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.
Sources
- 1.Ohno, T. (1988). Toyota production system: Beyond large-scale production. Cambridge, MA: Productivity Press.
- 2.Rother, M., & Shook, J. (2003). Learning to see: Value stream mapping to add value and eliminate muda. Cambridge, MA: Lean Enterprise Institute.
You have read it. What now?
Cite this page
ScholarGate. (2026, June 3). Kanban. ScholarGate. https://scholargate.app/operations-management/kanban