Kanban in Manufacturing: Beyond the Sticky Notes

Most Kanban implementations I've seen fail in the same way: someone attends a Lean training, comes back energized, puts sticky notes on a whiteboard, calls it a Kanban system, and then wonders why nothing changed. Six months later the board is ignored and the team is back to pushing product based on a weekly schedule guess.

Kanban is not a visualization tool. It's a replenishment signaling system — a mechanism for letting actual demand pull production rather than forecast push it. When designed correctly, it reduces lead time, improves availability, lowers inventory carrying costs, and makes production scheduling dramatically simpler. When designed incorrectly, it's just a wall decoration.

"The goal of Kanban is not to manage inventory. It is to expose the true pace of demand and respond to it with discipline."

The Core Principle: Pull, Don't Push

Traditional push scheduling works like this: someone forecasts demand, builds a schedule, and production makes what the schedule says regardless of what's actually being consumed. The result is inventory in the wrong place, at the wrong time, in the wrong quantities.

Pull systems work in reverse. Nothing is produced until a downstream signal authorizes it. A Kanban card, empty bin, or electronic signal from the point of consumption triggers replenishment. Production responds to real demand, not a forecast.

Step-by-Step: Designing a Kanban System That Works

Step 1: Choose Your Items Carefully

Not everything belongs in a Kanban system. The best candidates share these characteristics:

• Relatively stable, predictable demand (coefficient of variation below ~0.5)
• Short replenishment lead times relative to demand variability
• High enough volume to justify the design effort
• Significant enough availability impact to warrant pull discipline

Low-volume, highly variable, or very long lead-time items are often better managed through min/max reorder points or MRP. Trying to Kanban everything is a common mistake.

Step 2: Calculate Your Kanban Parameters — Do the Math

This is where most implementations fail. People eyeball the bin sizes rather than calculating them, and then wonder why they're constantly stocking out or drowning in inventory. The core formula:

Step 3: Design the Signal — Physical or Electronic

The signal is the heartbeat of the system. It must be:

• Visible — anyone on the floor can see the state of the system at a glance
• Simple — returning a card or moving a bin takes seconds, not minutes
• Disciplined — the signal must travel immediately when triggered, not at the end of the shift

For most manufacturing environments, a two-bin physical system is the right starting point. Bin A is in use; when it empties, it becomes the replenishment trigger and Bin B takes over. The empty bin goes back to production. When it returns full, the cycle repeats.

Step 4: Train for Discipline, Not Just Awareness

Kanban training that covers only "here's how it works" produces a team that understands the concept but breaks the system under pressure. The training must also cover:

• What to do when a signal is ignored or delayed
• How to escalate when replenishment isn't happening on time
• Why overproducing "just in case" defeats the entire system
• How individual signal discipline connects to customer availability

Step 5: Run Parallel Systems Before Cutover

For high-risk product lines, run the Kanban system in parallel with your existing scheduling for two to four weeks. This surfaces gaps in your parameter calculations without risking stockouts. It also builds team confidence before the old system is turned off.

Step 6: Review and Recalibrate Regularly

A Kanban system that was perfectly tuned six months ago may be wrong today. Demand patterns shift, lead times change, new products are added. Build a quarterly review into your standard work: check actual versus calculated consumption, adjust quantities if needed, and confirm signals are being processed with the right discipline.

The Most Common Failures — and How to Avoid Them

• Skipping the math. Intuitive bin sizes lead to chronic stockouts or excess inventory. Calculate.
• Not enforcing signal discipline. One supervisor who lets signals pile up until the end of the day breaks the whole loop. Signal timing is non-negotiable.
• Kanbanning everything. Highly variable, low-volume items don't belong in a pull system. Be selective.
• Never recalibrating. A Kanban system needs maintenance like any other process. Schedule the review.
• Treating it as a project with an end date. Kanban is an operating discipline, not an initiative. It runs indefinitely or it doesn't run at all.

Done right, Kanban simplifies your operation and makes customer availability a predictable outcome rather than a daily scramble. The sticky notes are optional. The discipline is not.

— Scott Hacker, MBA | Quality & CI Manager | Kansas City, MO