Organisations implement kanban to reduce inventory and compress lead times. They buy coloured bins, print laminated cards, and train operators on the rules of pull logistics. The logic is elegant: empty bins trigger replenishment, cards authorise production, and work-in-process stays strictly bounded. For a brief pilot period, inventory drops and flow improves.
Six months later, the same floor runs a push system decorated with kanban cards. Bins overflow because operators fear stockouts. Supervisors schedule production based on MRP forecasts, ignoring downstream pull signals entirely. The discipline required to maintain the pull logic vanished weeks after the kickoff event.
This degradation is not a failure of the kanban methodology. It is a structural failure of organisational governance. I have audited plants where the pull system decayed so thoroughly that the cards served no operational purpose. The decay follows a predictable, five-stage pattern that you can diagnose within an hour of walking any shop floor.
The Five-Stage Decay of a Pull System
Every kanban implementation begins with a controlled pilot. Two workstations, one product family, and intense oversight yield immediate gains. Inventory falls by thirty percent. Lead times compress. Management authorises a full rollout based on this isolated success, ignoring the fact that the pilot bore no resemblance to the complexity of the actual production floor.
The rollout proceeds without daily ownership. A cross-functional team maps the value stream, labels bins, and conducts training. Then the team disbands. There is no audit cadence and no escalation path when operators inevitably improvise. A lost card gets replaced without removing the original from circulation. Now two signals authorise one slot, and the system quietly oversupplies.
The first operational emergency calcifies the broken state. A machine goes down, or a key customer demands an expedite. The kanban system dictates stopping production because the downstream buffer is full. The supervisor, facing a screaming customer and an empty shift schedule, overrides the pull signal and runs the line anyway. The temporary workaround becomes the permanent operating standard.
The Lifecycle of Kanban Erosion
- 01Pilot SuccessIsolated conditions yield immediate inventory drops and justify a full rollout.
- 02Governance VacuumThe implementation team disbands; nobody owns the daily integrity of the pull signals.
- 03Emergency OverrideA valid short-term workaround becomes the default response to any daily production pressure.
- 04Metric ConflictUtilisation and output targets actively penalise operators for honouring kanban limits.
- 05FossilisationCards and bins remain on the floor as archaeological artifacts with zero functional authority.
Metrics formalise the dysfunction. Most facilities measure operator utilisation, daily output, and schedule attainment. Kanban compliance actively penalises all three. When pull logic dictates stopping production to respect a downstream constraint, utilisation drops and on-time delivery takes a hit. Operators and supervisors are rational actors; they optimise for what you measure.
The Mathematics of Card Proliferation
A kanban system is a closed-loop control mechanism. The number of cards in circulation dictates maximum work-in-process inventory. This count relies on demand rate, replenishment lead time, and a safety factor. Changing any of these variables without adjusting the card count causes the system to drift from its calibrated baseline.
Most organisations set card counts during the initial launch and never recalculate them. Demand shifts over time. Lead times fluctuate as suppliers change. New products are introduced, and old products are retired. But the card count remains frozen at a number calculated eighteen months ago under conditions that no longer exist on the shop floor.
Stale parameters guarantee systemic failure. Too many cards for current demand causes overproduction. Too few cards for increased demand starves downstream operations. Both outcomes look like kanban failure, but the root cause is organisational neglect. The mathematics were executed once and treated as permanent truth rather than a parameter requiring quarterly recalculation.
The Authority Gap in Pull Logistics
The most common failure mode in kanban is structural: people simply do not honour the cards. The reasons are rooted in performance management. An operator receives a signal to produce, but the shift supervisor has a daily output target set without reference to the pull system. The materials handler is evaluated on keeping lines stocked, not on respecting pull limits.
Every role on the floor has been given performance expectations that predate the kanban implementation. The pull logic was layered on top of existing metrics without removing or modifying them. When a kanban limit conflicts with a planner's MRP-driven schedule, the schedule wins because it is tied to the primary performance review.
The cards are the lowest-authority instruction on the shop floor, and everyone knows it.
Fixing this requires realigning every performance metric so the kanban system operates as the true production control, not a suggestion box. This means daily output targets must be derived from the pull logic, not imposed on it from a forecast. Escalation paths must trigger engineering or maintenance responses, not mandates to run faster and ignore the constraint.
Electronic Kanban: The Expensive Distraction
When paper cards fail, organisations often deploy electronic kanban systems. They invest in barcode scanners, RFID tags, and digital dashboards. The reasoning is seductive: if the problem is lost or ignored cards, digitising the signals will force compliance through superior tracking. The investment is framed as a technological upgrade to a human problem.
Electronic kanban solves the card-tracking problem without addressing the underlying discipline deficit. A digital signal instructing an operator to stop is ignored just as easily as a laminated paper card. The difference is that the digital system requires IT maintenance, software licenses, and generates automated reports that nobody in operational management actually reads.
The failure mode remains identical. Supervisors override the system during shortages. Operators work around the scanners. The electronic system adds visibility without adding operational authority. You can see exactly how non-compliant your organisation is on a high-resolution screen. This is surveillance applied to a structural problem that requires metric realignment, not new hardware.
Building Functional Pull Logic
A functioning kanban system looks deliberately boring. When you walk a floor with a working pull system, you see stations that are sometimes idle. Nobody panics, because the idleness means the downstream constraint is being respected. Supervisors check the kanban board before consulting the MRP report, and operators stop production when buffers are full without fear of reprisal.
Broken vs. Functional Kanban Governance
What broken systems do
- Card counts are set once and never recalculated.
- Utilisation and output targets override pull signals.
- Emergency overrides become the standard operating mode.
- Daily floor governance is owned by nobody.
What functional systems do
- Card counts are recalculated quarterly against actual demand.
- Daily targets are derived directly from the pull system.
- System stops trigger engineering and maintenance response.
- A dedicated process owner audits signal integrity weekly.
Functional systems are actively maintained. Card counts are reviewed quarterly. Demand changes trigger immediate recalculation. New product introductions include kanban sizing as a mandatory launch checklist item. Crucially, the system has a designated owner with the authority to reject overrides from sales, planning, or supervision when those overrides break the pull logic.
I have seen plants achieve this state by tying operational discipline directly to quality metrics. When a facility enforces a strict WIP cap, defect routing becomes faster and root-cause analysis is triggered by the system rather than by a delayed 8D report. Process stability rises because the pull system forces constraints into the open, whether those constraints are machine reliability or supplier capability.
The Operational Humility Required for Pull
Succeeding with kanban requires giving up the illusion of centralised control. A push system provides comfort: management sets the schedule, pushes the work, and measures the output. A pull system surrenders that control. The pace of production is dictated by actual customer demand, filtered through a closed-loop mechanism that you cannot override without permanently eroding its authority.
Organisations that succeed have made this philosophical shift. They accept that the pull system understands optimal production flow better than any planner's forecast. They restructure their metrics to reward system compliance over individual heroics. They give the kanban signals the highest authority on the shop floor, superseding the supervisor's target and the expediter's panic.
Kanban is not a visual management tool. It is an operational discipline. The tool is a card and a bin. The discipline is honouring what the card dictates, even when every other signal in the organisation screams to push more work into the system. Overriding the logic once establishes a precedent that destroys the system's authority forever. Protect the signal, or accept the inventory.