If you read our last guide on WIP Limits, you learned the critical rule of Lean flow: if you want to reduce lead time, you must stop starting and start finishing.
But how do you actually execute that on a bustling shop floor or a chaotic office? You can’t just walk around yelling “Stop working!” People need a system. They need clear, visual rules that tell them exactly when to produce, exactly what to produce, and most importantly, exactly when to stop.
That system is Kanban.
Invented by Taiichi Ohno at Toyota in the 1940s, Kanban (Japanese for “signboard” or “visual signal”) is the mechanism that enforces WIP limits and transforms your operation from a chaotic Push system into a synchronized Pull system. In this guide, we will break down exactly how Kanban works, how it physically controls inventory, and how you can implement it in both manufacturing and knowledge work.
1. The Paradigm Shift: Push vs. Pull Systems
To understand Kanban, you must first understand the disease it cures: The Push System.
In a traditional Push system, production is driven by a master schedule or a forecast. If the schedule says “Make 500 widgets today,” Machine A will make 500 widgets and push them to Machine B, regardless of whether Machine B is ready for them. This creates massive piles of unneeded inventory, hiding defects and tying up cash.
Kanban creates a Pull System. In a Pull system, nobody does any work until the downstream customer (the next machine in line, or the final buyer) explicitly asks for it. Production is driven by actual consumption, not a guess.
Push forces inventory into the system regardless of need. Pull uses Kanban signals to only replace what was consumed.
In the animation above, notice how the Pull System never overproduces. Because it uses a strict WIP Limit of 1, Machine A is forced to stop working until Machine B sends a “Kanban Signal” saying it is ready for the next piece. This completely eliminates overproduction.
2. The Kanban Board (Knowledge Work & Office)
The most famous application of Kanban in the modern era is the digital Kanban Board, popularized by Agile software development (using tools like Jira or Trello).
A Kanban board makes invisible knowledge work visible. It breaks a workflow down into columns (e.g., To Do, In Progress, Done). But a board full of sticky notes is not a Kanban system unless it has WIP Limits.
Try it out: In the interactive board below, the Development column has a hard WIP limit of 3. Try to click the tasks in the Backlog to pull them across the board.
Interactive Kanban: Click a task to pull it forward. Notice how WIP limits physically block you from overloading the system.
Notice how the system physically blocked you from pulling a 4th task into Development? That is the magic of Kanban. By preventing developers from pulling new work, it forces them to focus on finishing the tasks already in progress. It protects the team from burnout and ensures work flows quickly from left to right.
3. Kanban on the Factory Floor (Physical Signals)
On a manufacturing floor, Kanban rarely looks like a Trello board. Instead, it relies on physical cues—cards, empty bins, or painted squares on the floor—to send the pull signal upstream.
Here is how the continuous Kanban loop works:
- Consumption: The downstream process (the customer) takes a part out of a designated storage area (often called a “Supermarket”).
- The Signal: Taking the part frees up a physical Kanban card (or leaves an empty bin). That card is sent upstream to the supplier.
- Production: The upstream process receives the card. This is their authorization to work. They produce exactly what the card asks for—no more, no less.
- Replenishment: The newly made part is placed back into the Supermarket with the card attached, ready for the next consumption.
The Kanban Information Loop: The downstream customer consumes a part, triggering an empty card to flow upstream, authorizing production.
Because the number of Kanban cards in circulation is strictly limited, the total Work in Progress is permanently capped. You can never have more parts in the system than you have cards.
4. The Two-Bin System (Inventory Control)
One of the most effective and universally applied physical Kanban systems is the Two-Bin System, often used for screws, bolts, and small inventory on assembly lines.
Instead of manually counting screws every Friday to see if you need to order more, the bins themselves act as the Kanban signal.
How it works: Click the “Consume” button below to empty the front bin. Watch what happens when the bin hits zero.
The Two-Bin System is the simplest physical Kanban loop used on shop floors.
The genius of the Two-Bin system is its simplicity. The operator never has to count anything. They pull from the front bin until it is empty. The empty bin is the Kanban card. It is sent to purchasing to trigger a reorder. While the new order is being processed, the operator pulls seamlessly from the reserve bin. Stock-outs are eliminated, and inventory holding costs are slashed.
5. Real-World Kanban Scenarios
Kanban is highly adaptable. Here is how different industries apply the exact same pull-system logic.
1. The Manufacturing Cell
A CNC machining cell uses painted “Kanban squares” on the floor between workstations. If the square is full, the upstream machine stops cutting. The operators use the extra time to perform maintenance or 5S cleaning, rather than overproducing parts.
2. The Hospital ER
An emergency room uses a visual board with magnetic cards to track patient rooms. Doctors cannot pull a new patient from the waiting room until an exam room is cleared and cleaned. The physical space is the WIP limit, preventing the ER from collapsing into chaos.
3. The Coffee Shop
A barista writes your order on a physical cup and slides it down the rail. The espresso machine operator only pulls an empty cup when they have finished the previous one. The cup acts as the Kanban card, ensuring the machine is never overloaded and drinks stay hot.
4. Corporate Procurement
An IT department uses a digital Kanban board for laptop requests. They set a limit of 5 active requests in the “Purchasing” column. If an executive demands a new laptop, they can clearly see it is 6th in the backlog, setting realistic lead-time expectations.
6. Action Plan: Implementing Your First Kanban
Kanban is an evolutionary change method. You do not need to rewrite your entire corporate structure to start using it today.
Start with What You Do Now
Map the current stateKanban does not require changing your processes. Simply visualize your existing workflow. Draw columns on a whiteboard for every step of your process, from “Requested” to “Done.” Have your team write every active task on a sticky note and place it in the current column.
Look at the most crowded column. Agree as a team on a maximum number of items allowed in that state. A common industry rule of thumb for knowledge work is WIP Limit = (Number of Team Members × 1.5). For physical manufacturing, start by referencing a basic safety stock calculation to set your bin quantities. Make the limit slightly painful, but achievable, and write it clearly at the top of the column.Calculate Initial WIP Limits
Stop the bleeding
During your daily stand-up meeting, walk the board from right to left (focusing on items closest to being done). If a column is at its WIP limit, the team must swarm the blockage to clear it before anyone is allowed to pull new work from the backlog.Manage the Flow
Watch the signals
Write clear rules underneath each column stating exactly what conditions must be met before a card is allowed to be pulled into the next column. This prevents defective or incomplete work from being pushed downstream.Make Policies Explicit
Define 'Done'
7. Measuring Success: Core Kanban Metrics
Kanban is inherently data-driven. To prove your pull system is actually working and continuous improvement is happening, you need to track the “Big Three” flow metrics:
Lead Time
The total time from when a customer requests an item (or a task enters the backlog) to when it is fully delivered. This is what your customer cares about most.
Cycle Time
The active working time it takes for your team to complete an item once it is pulled out of the backlog and into the “In Progress” column. It measures your execution speed.
Throughput
The number of items (parts, features, tickets) successfully finished per unit of time (e.g., 15 tasks per week). It measures your system’s overall capacity.
💡 Pro Tip: Visualizing Flow with CFDs
Data-driven teams track these metrics visually using a Cumulative Flow Diagram (CFD). A CFD plots the number of items in each column over time. A widening band on the chart instantly highlights where work is piling up, making it the ultimate tool for diagnosing bottlenecks before they cripple your overall lead time.
8. Conclusion
A Kanban system is the bridge between the theory of flow and the reality of daily execution. Whether you are dealing with physical widgets on an assembly line or digital code in a software sprint, Kanban provides the necessary boundaries to keep your system healthy.
By making work visible and enforcing strict limits on what can be started, you empower your team to stop context-switching, stop overproducing, and finally focus on delivering value to the customer at maximum speed.
References & Further Reading
- Ohno, T. (1988). Toyota Production System: Beyond Large-Scale Production. Productivity Press. (The foundational text from the inventor of Kanban).
- Anderson, D. J. (2010). Kanban: Successful Evolutionary Change for Your Technology Business. Blue Hole Press. (The definitive guide to adapting Kanban for knowledge work and software).
- Sugimori, Y., Kusunoki, K., Cho, F., & Uchikawa, S. (1977). Toyota production system and Kanban system Materialization of just-in-time and respect-for-human system. International Journal of Production Research, 15(6), 553-564. (The original academic breakdown of the system).
