The Signal That Stopped
Signaling
You implemented Kanban. You bought the bins. You printed the cards.
You trained the operators. The sensei nodded approvingly during the
kickoff event, and for about six weeks, everything looked like the
textbook illustrations. Cards moved. Bins flowed. The factory floor had
a visible rhythm that made visitors reach for their cameras.
Then, slowly and then all at once, the cards stopped meaning
anything.
Operators pulled cards before the bins were empty “just in case.”
Supervisors overrode the system when it told them something they didn’t
want to hear. The card racks filled up with expired signals nobody
cleared. Maintenance kept producing parts because the machine was
available, not because anyone needed them. The Kanban system — your pull
system, your visual control, your flow management tool — had become a
push system wearing a Kanban costume.
And nobody noticed. Or rather, everybody noticed, but nobody had the
authority or the willingness to say it out loud. The Kanban cards were
still there, dutifully attached to bins, so the system must be working.
The reports still showed “Kanban compliance” at 94%. The auditors
checked the boxes. But the inventory in the warehouse kept growing. The
lead times kept stretching. The expedite freight bills kept mounting.
And the quality problems — the ones Kanban was supposed to surface by
limiting exposure to defective batches — kept getting buried under the
sheer volume of material nobody had authorized but everybody had
accepted.
This is what Kanban failure looks like. Not a dramatic collapse, but
a gradual, comfortable, mutually agreed-upon fiction that the system is
working because the artifacts of the system are still present.
What
Kanban Actually Is (Before We Discuss How It Breaks)
Kanban is a pull-based production control system originally developed
at Toyota as part of the Toyota Production System. The word itself means
“signboard” or “billboard” in Japanese, and the concept is elegant in
its simplicity: downstream processes withdraw only what they need, when
they need it, from upstream processes. The Kanban card is the signal —
the authorization — for production or replenishment.
The system operates on a few fundamental rules:
- No production without a Kanban card. If you don’t
have a signal, you don’t make parts. - Production exactly matches the quantity on the
card. Not approximately. Not “roughly.” Exactly. - Cards circulate. They move with material, they
return when material is consumed, they trigger the next cycle. - The number of cards is deliberately limited. This
is the entire point. The limit creates the constraint that exposes
problems. - Cards are visible. Anyone walking the floor can see
the status of production at a glance.
In a quality management context, Kanban serves a purpose beyond
scheduling. By limiting the amount of work-in-process (WIP) between
stages, it limits the blast radius of quality problems. If a welding
cell produces defective parts and the downstream buffer is two hours of
Kanban-controlled inventory, you discover the problem after two hours of
production — not after two days. The constraint is a quality feature,
not just a scheduling tool.
This is the theory. The practice, as most manufacturers discover, is
something else entirely.
The Six Ways
Kanban Systems Fail in Practice
1.
Card Inflation: When “Just in Case” Becomes “Just Too Many”
The most common failure mode begins with the best of intentions. A
supervisor notices that the Kanban system sometimes causes brief
stockouts when demand spikes or when a machine goes down. The natural
human response is to add more cards — to increase the buffer. One more
card. Then two. Then five.
Each additional card weakens the signal-to-noise ratio of the system.
Kanban works precisely because the constraint forces problems to
surface. When you add cards, you delay problem exposure. The stockouts
don’t go away — they just become less frequent and more mysterious when
they do occur, because the buffer has masked the root cause.
In quality terms, this is the equivalent of widening your control
limits until every process looks in control. You haven’t improved the
process; you’ve just made it harder to detect when something is wrong.
The cards have become a safety blanket rather than a control
mechanism.
I’ve seen factories where the original Kanban design called for 12
cards between two operations and the actual count, after three years of
incremental “adjustments,” was 47. The system was still technically a
Kanban system. Cards still circulated. Operators still followed the
motions. But the pull signal had become meaningless — the upstream
process was essentially running continuously, which is to say, it had
become a push system with decorative cards.
2. Shadow
Systems: When People Work Around the Kanban
The second failure mode is the shadow inventory system. This happens
when operators and supervisors, frustrated by the constraints of the
Kanban system, develop informal workarounds that exist alongside the
formal system.
A common pattern: the Kanban says don’t produce, but the machine
operator knows that the next order will eventually need the parts, so
they run them anyway and stash the excess in a hidden location — behind
the machine, in a maintenance closet, in an unmarked rack in the
warehouse. The parts aren’t on any Kanban card, but they exist, and
they’ll be used when the formal system finally authorizes production. By
then, nobody remembers how old they are, what lot they came from, or
whether they passed inspection.
From a quality standpoint, this is catastrophic. Shadow inventory
bypasses every control you’ve built. Parts that were never formally
produced can’t be formally traced. Defects in shadow batches can’t be
correlated to process conditions because the production was never
recorded. First-in-first-out (FIFO) becomes impossible because the
shadow stock doesn’t follow the same flow as the formal stock.
The shadow system exists because the formal system has lost
credibility. People don’t bypass systems that work. They bypass systems
that feel arbitrary, that create friction without visible benefit, that
make their jobs harder without making outcomes better. The existence of
a shadow system is not a discipline problem — it’s a design feedback
signal that the Kanban system has drifted out of alignment with
reality.
3. Signal
Degradation: When the Card Becomes a Label
A Kanban card is supposed to be a dynamic, circulating signal. It
carries information: part number, quantity, source, destination, and —
critically — the authorization to act. When the system works, the
absence of a card is as meaningful as its presence. No card means no
production. No signal means no withdrawal.
In practice, cards accumulate. They get pinned to bulletin boards as
“reference.” They get filed in drawers because someone might need them.
They get photocopied because the original got damaged and now there are
three cards where there should be one. They get laminated, framed, and
displayed for visitor tours — a static exhibit of what a Kanban card
looks like, rather than a functioning signal.
The degradation is gradual. First, the card stops circulating and
becomes a label — permanently attached to a bin, never removed, never
returned. Then the quantity on the card stops being the actual
withdrawal quantity — operators take what they need and leave the rest.
Then the card stops being the authorization for production — the
production schedule (a push document) takes over, and the card becomes a
tracking artifact with no decision authority.
At this point, you don’t have a Kanban system. You have bins with
labels on them. Which is fine if that’s what you want, but it is not a
pull system, it provides no flow control, and it offers zero quality
protection through WIP limitation.
4. The
E-Card Illusion: Digital Kanban Without Discipline
Many organizations have migrated from physical cards to electronic
Kanban systems — barcode scanners, RFID tags, MES-integrated signals,
dashboard-driven alerts. The technology is sound. The implementation
usually isn’t.
The failure mode is the same as with physical cards, but faster and
more scalable. Digital Kanban systems make it trivially easy to override
signals, adjust quantities, add cards, and bypass constraints with a few
keystrokes instead of a physical act that would be visible to everyone
on the floor. A supervisor who would think twice about physically adding
ten cards to a rack will click “increase Kanban count by 10” without
hesitation.
Worse, digital systems create the illusion of precision. The
dashboard shows real-time Kanban status with colorful indicators and
trend charts. It looks authoritative. But the underlying data is only as
good as the inputs — and if operators are scanning cards out of
sequence, marking withdrawals retroactively, or batch-updating the
system at the end of shift, the beautiful dashboard is displaying
fiction with high-resolution graphics.
Electronic Kanban also tends to disconnect the signal from the
physical reality. With physical cards, the constraint is tangible — you
can see the empty rack, feel the absence of signal, and understand
viscerally that the system is telling you to stop. With digital Kanban,
the signal is an alert on a screen that can be dismissed with a click.
The authority of the signal depends entirely on whether people choose to
respect it, and digital signals are easier to ignore than physical
ones.
5.
Supplier Kanban Breakdown: When the Pull Stops at Your Door
The Kanban principle is supposed to extend upstream to suppliers.
Instead of placing fixed orders, you send Kanban signals that authorize
shipment of specific quantities at specific times. This smooths demand,
reduces bullwhip effects, and creates a synchronized supply chain.
In practice, supplier Kanban systems fail for one of two reasons.
Either your demand is too erratic for the supplier to respond to Kanban
signals (meaning your internal production isn’t actually leveled, which
undermines the entire TPS foundation), or the supplier treats the Kanban
as a purchase order and ships ahead of schedule to “be safe” —
reintroducing the push dynamic you were trying to eliminate.
When suppliers push material, your receiving dock becomes a buffer
zone. The Kanban said withdraw 500 units; the supplier shipped 2,000
because they had a machine available and wanted to keep it running. You
accept the excess because rejecting it would cause a diplomatic
incident, and now you have 1,500 units of uncontrolled inventory that
will sit in your warehouse, age past their shelf life, or get mixed with
newer stock — creating a quality traceability nightmare.
6.
Quality Buffer Abuse: When WIP Becomes a Quality Crutch
This is the most insidious failure mode, and it directly undermines
the quality management purpose of Kanban.
Limited WIP between processes is supposed to expose quality problems
quickly. When a defect occurs, the small buffer means it reaches the
next process rapidly, where it’s detected, and corrective action is
initiated with minimal scrap and clear root cause correlation.
But when the Kanban system degrades and WIP grows — through card
inflation, shadow systems, or supplier pushing — the enlarged buffers
become quality crutches. Defects take longer to reach detection. The
defective parts sit in buffers for hours or days, accumulating alongside
parts from multiple production runs. When the defect is finally found,
the trail is cold. Which machine? Which operator? Which lot of raw
material? The investigation stalls because the temporal separation
between production and detection has destroyed the evidence.
The buffer isn’t just hiding quality problems — it’s actively
preventing you from solving them. And the larger the buffer, the more
confident people become that the process is “working” because defects
aren’t reaching the customer. They are reaching the customer, of course
— just slowly, in delayed batches, with root causes that will never be
identified.
The
Organizational Dynamics of Kanban Failure
Kanban systems don’t fail because the cards are wrong or the formulas
are incorrect. They fail because of organizational dynamics that the
Kanban system exposes but the organization refuses to address.
Production pressure overrides system discipline.
When customer demand is high and machines are running, the pressure to
produce overrides the discipline of waiting for a Kanban signal. The
logic is seductive: “We know we’ll need these parts, so why wait?” But
every unauthorized production breaks the synchronization that makes the
system work.
Performance metrics conflict with Kanban principles.
If you measure operators on utilization (keeping machines running) or
output (parts produced per shift), Kanban’s deliberate idleness looks
like inefficiency. The operator who correctly waits for a Kanban signal
is penalized for low utilization, while the operator who runs ahead and
builds shadow inventory is rewarded for high output. The measurement
system actively punishes compliance with the pull system.
Management doesn’t trust the system. Kanban requires
the willingness to stop — to let a machine sit idle when there’s no
signal, to let an operator wait when the downstream process isn’t ready.
This requires trust that the system is correctly designed and that the
constraints are intentional. Most managers don’t have this trust. They
see idle machines and intervene, overriding the system and teaching
everyone that the Kanban is a suggestion, not a rule.
The system is never recalibrated. Kanban card counts
and buffer sizes should be recalculated regularly as demand patterns,
process capabilities, and cycle times change. In practice, the initial
calculation is done once (usually by a consultant who has since
departed), and the system runs on autopilot for years. When the
underlying conditions change — a new product mix, a different cycle
time, a quality improvement that reduces the needed buffer — the Kanban
system still reflects the old reality.
The Quality
Manager’s Role in Kanban Integrity
Quality managers often treat Kanban as a production or logistics tool
— someone else’s responsibility. This is a mistake. Kanban directly
affects quality outcomes in at least four ways:
- Detection speed. Small buffers mean faster defect
detection. Large or uncontrolled buffers mean slower detection and
weaker root cause correlation. - Traceability. Material that flows through a
disciplined Kanban system has clear provenance. Material from shadow
systems or unauthorized production doesn’t. - Process stability. Kanban is supposed to level
production, which stabilizes processes, which improves quality. A
degraded Kanban system amplifies variability instead of dampening
it. - Problem exposure. The constraint embedded in a
well-functioning Kanban system forces problems to the surface — not just
production problems, but quality problems. Kanban that isn’t
constraining isn’t exposing.
The quality manager should be an active participant in Kanban system
design, periodic recalibration, and — most importantly — in monitoring
the integrity of the pull system as a leading indicator of quality risk.
When cards start accumulating, when buffers grow, when shadow systems
appear, the quality organization should treat these as early warning
signals that quality problems are being masked and will emerge later in
larger, harder-to-diagnose form.
Diagnosing
Your Kanban System: A Practical Checklist
If you’re running a Kanban system, here’s how to assess whether it’s
still a pull system or has become a push system in disguise:
- Count the cards. How many Kanban cards exist for
each part number? Compare to the original design calculation. If the
count has drifted upward by more than 20% without a formal
recalibration, you have card inflation. - Walk the floor and look for unauthorized inventory.
Are there parts stored outside the Kanban system? Are there bins without
cards? Are there stashes behind machines? Shadow inventory is the
clearest sign that the formal system has lost credibility. - Observe production starts. Does every production
run have a corresponding Kanban signal? Or do some runs start based on a
schedule, a verbal order, or “we always run this on Tuesdays”? - Check card circulation. Pick ten cards at random.
Are they where they should be based on the material flow? Or are they
pinned to boards, filed in drawers, or sitting in offices? - Measure the signal-to-action delay. When a Kanban
card is returned to the production authorization rack, how long does it
take for production to start? If the answer is “immediately, because the
operator was already running,” you have a push system. - Ask operators what happens when they run out of
cards. If the answer is anything other than “I stop production
and notify my supervisor,” the system has lost its authority.
The Path Back to Pull
Recovering a degraded Kanban system is harder than implementing one
from scratch because you have to undo established habits and dismantle
shadow systems that people have come to depend on. The process
requires:
Leadership commitment to the pull principle. This
means accepting that machines will sometimes be idle and operators will
sometimes wait, and not treating this as a problem to be fixed. It means
measuring compliance with the Kanban system as a leading indicator of
flow health.
A formal card audit and recalibration. Every card
count, every buffer size, every circulation rule should be reviewed
against current demand and process data. Cards should be removed, not
added — the bias should always be toward tighter constraints that expose
problems faster.
Shadow system elimination. This requires
understanding why the shadow systems exist. If operators are hoarding
parts, it’s because the formal system doesn’t reliably provide what they
need when they need it. Fix the reliability, and the shadow systems
become unnecessary.
Regular system integrity reviews. Not an annual
audit where someone walks through with a clipboard, but a monthly review
of Kanban circulation data, buffer levels, and production authorization
patterns. The goal is to detect degradation early, before it becomes the
new normal.
Conclusion: The System
Is the Discipline
Kanban is not a set of cards. It’s not a scheduling algorithm. It’s
not a set of bins on a factory floor. Kanban is a discipline — the
discipline to produce only what is needed, only when it is needed, only
in the quantity that is needed. The cards, the bins, and the circulation
rules are tools that support the discipline. They are not a substitute
for it.
The tragedy of Kanban failure is that the system usually works well
enough at the beginning to build confidence, and then degrades slowly
enough that the deterioration is invisible. By the time the problems
become obvious — rising inventory, stretching lead times, recurring
quality issues with no traceable cause — the system has been broken for
so long that nobody remembers what working looks like.
The organizations that maintain Kanban integrity over decades don’t
do it through better formulas or fancier software. They do it through a
culture that respects the signal — that treats the absence of a Kanban
card as meaningful information rather than an obstacle to work around.
They do it through leadership that understands the difference between a
busy factory and an effective one. And they do it through quality
organizations that recognize Kanban not as a logistics tool, but as a
foundational element of their quality management architecture.
Your Kanban system is either a constraint that protects you from
yourself, or a decoration that makes you feel better while the problems
accumulate. Which one it is depends entirely on whether you have the
discipline to let it do its job.
About the Author: Peter Stasko is a Quality
Architect with over 25 years of experience in manufacturing quality
management, process optimization, and continuous improvement. He has
implemented and audited Kanban systems across automotive, electronics,
and medical device industries, and has seen every possible way a
well-designed pull system can be quietly dismantled by good
intentions.
