Kanban
Term 122 of 268 · Topic
In one sentence
Kanban is a visual workflow management method that uses cards and columns to signal what to produce and when, based on actual demand. It limits work in progress to prevent overproduction and expose bottlenecks.
Reviewed by Juan Manuel Garrido
Co-founder of VantegrateLinkedIn
Kanban definition
Kanban (Japanese for "visual card" or "signal") is a workflow management method that coordinates production and replenishment using visual signals: a card, a column or an empty container indicates when and how much needs to be made or restocked. Its core principle is to produce only what the next stage consumes, so inventory nobody asked for does not pile up.
Born in the Toyota Production System in the 1950s, Kanban is one of the pillars of Lean manufacturing and a concrete example of a pull system (triggered by demand), as opposed to pushing production against a forecast. In plants that digitize their operations, it is part of what brings order to Manufacturing, where the board stops being made of cardboard and starts syncing with the ERP and the shop floor.
Beyond the factory, the same concept became popular in software and services teams as a board of columns (to do, in progress, done) that limits simultaneous work. In both worlds the idea is the same: make the work visible, limit what is in progress and move each unit only when there is capacity to receive it.
How a Kanban system works
The classic mechanics of a production Kanban rely on cards that travel with the material. Each container of parts carries a withdrawal card (it authorizes moving material from one stage to the next) and a production card (it authorizes making the batch that replaces what was consumed). When a workstation empties a container, it sends the card back upstream: that return is the order to produce. Nothing gets made without a card authorizing it, so total inventory is capped by the number of cards in circulation.
Three rules keep the system from getting out of control:
- Limit work in progress (WIP): each column or stage accepts a maximum number of units in process. When it fills up, it stops "pulling" new work until capacity frees up.
- Pull, don't push: a stage only produces when the next one has consumed. Actual demand, not a forecast, triggers every movement.
- Make the flow visible: the board shows where work piles up. An overloaded column reveals the bottleneck without the need for a report.
Why it matters for an operation
The value of Kanban is that it turns an invisible problem (excess inventory, unbalanced stages, stuck orders) into something you can see at a glance. By limiting work in progress, it reduces the capital tied up in stock, shortens cycle times and forces you to solve bottlenecks instead of covering them up with more inventory. It is also the operational foundation of practices such as Lean manufacturing, and it pairs with inventory turnover as a health metric.
A concrete example in Argentina
An auto parts maker in Córdoba's industrial belt that supplies a vehicle assembly plant moved from producing against a forecast (and piling up weeks of parts that were never ordered) to a Kanban scheme with standardized containers. Every time the assembly plant's line consumes a container of metal brackets, a signal fires that authorizes making exactly that replenishment batch. The typical result is less idle stock in the warehouse and fewer last-minute emergencies, because the plant produces at the pace of real consumption and not at the pace of a spreadsheet. In practice, many small and midsize manufacturers start with physical boards and move to digital boards connected to their management system as they grow.
Common mistakes
- Too many cards or a WIP limit set too high: if the limit is loose, inventory swells and the method loses its reason to exist. WIP is deliberately tuned downward.
- Using Kanban with very erratic demand or extremely slow-moving products: it works best with relatively stable, repetitive consumption; for extreme peaks, it is better to combine it with safety stock.
- A nice board, ignored rules: having columns is not Kanban. Without respected WIP limits and without pull logic, it is just a decorated to-do list.
Kanban vs MRP
Kanban and MRP are often presented as rivals, but they solve different things and many plants combine them: MRP plans what and when at an aggregate level, while Kanban regulates fine-grained replenishment on the floor.
| Aspect | Kanban | MRP |
|---|---|---|
| Logic | Pull (triggered by actual consumption) | Push (plans against a forecast) |
| Trigger | Card or empty container | Requirements calculated through a bill of materials explosion |
| Inventory | Low, capped by the cards | Depends on forecast accuracy |
| Best with | Stable, repetitive demand | Products with a complex bill of materials |
| Response to change | Immediate and local | Requires recalculating the plan |
In short, Kanban is a simple tool with a demanding discipline: its power is not in the cards but in respecting the limits and letting actual demand, not urgency, set the pace of the operation.
FAQs about Kanban
What is Kanban?
What is Kanban?
Kanban is a visual workflow management method that uses cards, columns or containers as signals to indicate what to produce or restock and when. Its core principle is to produce only what the next stage consumes, limiting work in progress to prevent overproduction and expose bottlenecks. It was born in the Toyota Production System in the 1950s and is now used in factories as well as in software and services teams.
What is the difference between Kanban and MRP?
What is the difference between Kanban and MRP?
Kanban is a pull system: every movement is triggered by actual consumption, through a card or a container that empties, and it keeps inventory capped. MRP is a push system that plans production against a forecast, calculating requirements from the bill of materials. Kanban works best with stable, repetitive demand, while MRP handles products with a complex structure better. Many plants combine them: MRP to plan at an aggregate level and Kanban to regulate replenishment on the floor.
What is the work in progress (WIP) limit in Kanban?
What is the work in progress (WIP) limit in Kanban?
The work in progress limit, or WIP limit, is the maximum number of units that can be in process at a stage or column at the same time. When that limit is reached, the stage stops accepting new work until it frees up capacity. It is the most important rule in Kanban: by capping what is in progress, you reduce tied-up capital, shorten cycle times and make bottlenecks visible instead of covering them up with more inventory.
Is Kanban only for factories?
Is Kanban only for factories?
No. Kanban was born in industrial production, but the same concept became popular in software, marketing and services teams as a board of columns (to do, in progress, done) that limits simultaneous work. In every case the logic is the same: make the work visible, limit what is in progress and move each unit only when there is capacity to receive it. The difference is that in a factory the cards travel with the physical material, while in a team they represent tasks.
When should you not use Kanban?
When should you not use Kanban?
Kanban works best with relatively stable demand and repetitive consumption. It is not the best option for very slow-moving products or very erratic demand, where signal-based replenishment can fall short when peaks hit. In those cases it is better to combine it with safety stock or rely on MRP-style planning. It also fails when the board is set up but the work in progress limits and the pull-by-demand logic are not respected: without that discipline, it stops being Kanban and becomes a simple to-do list.
This, applied to your plant
Production, quality and dispatch connected, with the data available without asking anyone for a report. Tell us what falls through the cracks between the plant and the system.
Related terms
- Lean ManufacturingLean manufacturing is a production management philosophy that aims to deliver more value to the customer while using fewer resources. It is built on eliminating the seven wastes in the process (overproduction, waiting, transportation, inventory, motion, overprocessing and defects) through continuous improvement.
- MRP (Material Requirements Planning)MRP (material requirements planning) is a method that calculates which materials to buy or produce, in what quantity and when, based on the production plan, the bills of materials and available inventory.
- Inventory TurnoverInventory turnover is a metric that measures how many times a company sells and replenishes its stock over a period. It is calculated by dividing the cost of goods sold by average inventory: the higher the turnover, the more efficiently inventory is being managed.
- Safety StockSafety stock is the extra inventory you keep as a buffer against demand variability and replenishment delays, to avoid stockouts when consumption or the lead time exceeds what was planned.
- OEE (Overall Equipment Effectiveness)OEE (Overall Equipment Effectiveness) is a metric that measures how productive a machine or line is: it combines availability, performance and quality into a single percentage. An OEE of 100% means making only good parts, at maximum speed, with no stops.
- TPM (Total Productive Maintenance)TPM (Total Productive Maintenance) is a management methodology that aims for zero breakdowns, zero defects and zero accidents by involving every employee, not just maintenance, in the autonomous care of equipment to maximize its availability and performance.
Manufacturing industry
Plant, quality and dispatch connected, with production data available without asking anyone for a report.
How we solve it in ManufacturingFive AI products that work on top of the CRM you already use. They don't replace your system: they add the layer you do by hand today.





