Kanban is a double-edged sword.

“Double-edged sword.” A type of sword that we didn’t use in Japan. It means that if we don’t use it properly, it could bounce back and hurt the user itself.

Kanban is a double-edged sword: if we don’t use it properly, it can hurt the organization.

If we don’t have leveization, the chaos will hurt the upstream.

If we apply it to large batch production, the bull-whip effect will kill the upstream.

If we don’t have the standardized work, the signal will scatter.

If we have a high defect rate and unstable processes, the Kanban becomes just noise.

Kanban doesn’t work is rarely the truth. The truth is we didn’t solve any problems.

Kanban is a double‑edged sword.

In Japanese history, we rarely used double‑edged swords. Most traditional blades were single‑edged, designed for a specific way of cutting and drawing. A double‑edged sword, on the other hand, cuts both ways. If you don’t handle it correctly, it can easily swing back and injure the person who is holding it.

Kanban is like that.

Used wisely, it reveals problems, stabilizes flow, and helps teams deliver value smoothly. Used carelessly, it amplifies chaos, hides real issues, and hurts the organization that adopted it.

In this post, I’ll explain why Kanban can be dangerous when misunderstood and walk through some common failure modes:

1. Lack of leveled work (Heijunka) creates chaos upstream.

2. Applying Kanban to large batches causes a bullwhip effect.

3. No standardized work turns signals into noise.

4. High defect rates and unstable processes make Kanban meaningless.

And finally, I’ll share the uncomfortable truth: “Kanban doesn’t work” is rarely the real problem. Usually, we just didn’t solve the underlying issues.

What Kanban Really Is (and Isn’t)

Kanban started as a simple signaling system in manufacturing, inspired by how supermarkets restock shelves. A Kanban card or signal says: “We’ve consumed this much. Please produce or supply this much.”

At its core, Kanban is:

• A way to visualize work and inventory.

• A pull system to prevent overproduction.

A mechanism to expose problems in flow.

When we forget this, Kanban becomes the double‑edged sword we don’t know how to handle.

Without Leveled Work, Chaos Hurts the Upstream

In TPS, leveled production is called Heijunka. The idea is simple: instead of processing work in big spikes and droughts, we smooth the flow over time.

When we use Kanban on top of un‑leveled work, we just make the chaos more visible without actually controlling it. Imagine this pattern:

• Sales pushes a big deal at the end of the month.

• A huge batch of work enters the system at once.

• Downstream teams get overloaded.

• Upstream teams are then starved, waiting for the next big batch.

You might have a beautiful Kanban board, but what you’re visualizing is turbulence.

If we don’t have leveled work, the chaos hurts the upstream:

• Suppliers or upstream teams are constantly switching priorities.

• Lead times become unpredictable.

• Everyone spends more time firefighting and less time improving.

Kanban will faithfully show the spikes and bottlenecks. But unless we address the leveling of demand, those signals just tell us how painful our system already is.

Large Batches and the Bullwhip Effect

Another common misuse is applying Kanban to large batch production.

The Kanban method assumes that we work in relatively small, regular chunks so that pull signals travel smoothly through the system. When we attach Kanban to large, infrequent batches, we create something called the bullwhip effect.

The bullwhip effect happens when small fluctuations in demand turn into huge swings upstream:

• A big batch order is placed.

• Downstream teams suddenly send large Kanban signals upstream.

• Upstream teams overreact, building inventory or capacity that may not actually be needed.

Despite the large inventory, we still experience ‘missing materials’ because we don’t have every item.

In this situation, the bullwhip effect kills the upstream:

• Upstream teams lose any sense of stable rhythm.

• Planning becomes guesswork.

• Improvement efforts stall because the system never settles long enough to study.

Kanban is not a magic layer you can slap onto a large‑batch system to make it “stable.” If the batch logic stays the same, Kanban only helps you see the bullwhip more clearly—it doesn’t remove it.

Without Standardized Work, Signals Scatter

Kanban relies on a shared understanding of how work is done. In lean terms, this is standardized work: the current best-known way to perform a task, documented and agreed upon.

When standardized work is missing, each person or team interprets the Kanban signals differently:

• One person pulls too much work at once, like batching sub-assembly work.

• Another waits for extra Kanban to come and wait.

A third skips certain steps entirely.

The result: the signal scatters.

Instead of a clear “pull” that moves work through defined steps, you get:

• Inconsistent cycle times

• Confusion about when work is truly “done” in each column

Frequent handoff problems

The presentation might look organized, but underneath, everyone is playing their own game. In this environment, Kanban can’t do its job. The card moves, but the work doesn’t flow.

Kanban should sit on top of at least a minimum level of standardization:

• Clear definitions of each work.

• Start according to the exact signal, sequence, timing, and quantity that Kanban provided.

• The only reason to stop is “No Kanban.”

Without this, the board becomes decoration rather than a control mechanism.

High Defect Rates Turn Kanban Into Noise

Kanban also assumes that our processes are stable. That doesn’t mean perfect, but it does mean that most of the time, work can move from start to finish without constant rework or failure.

If we apply Kanban on top of high defect rates and unstable processes, something else happens:

• Cards bounce back and forth between processes.

• “Done” items suddenly reappear in “In Progress” or “To Do.”

Urgent rework constantly preempts planned work.

In this environment, Kanban becomes just noise.

The Kanban is full of motion, but not much progress:

• Throughput is unpredictable.

• Lead times are long and highly variable.

• Teams lose trust in the signals because everything is an exception.

If every item is an emergency, no item is truly important. Kanban cannot compensate for fundamentally broken processes; it only reveals how broken they are.

“Kanban Doesn’t Work” Is Rarely the Truth

When organizations say, “Kanban doesn’t work for us,” it is rarely about Kanban itself.

More often, it means we:

• Didn’t level the work.

• Tried to keep large batches.

• Skipped standardized work and common rules.

Ignored instability and high defect rates.

In other words, we didn’t solve any of the real problems. The thinking was ‘just add more Kanban.” And created a hyperinflation of Kanban, which means no value in Kanban.

Kanban’s job is to expose those problems:

• Bottlenecks become visible.

• Delays and queues are obvious.

• Rework and defects show up as backflows.

That exposure can be uncomfortable. It’s tempting to blame the tool rather than face what it reveals.

How to Use the Double‑Edged Sword Safely

If Kanban is a double‑edged sword, how do we handle it without cutting ourselves?

Here are some practical steps:

Start by stabilizing.

Before tweaking Kanban numbers, focus on basic stability: reduce urgent rework, make work visible, and agree on what “done” means.

2. Level the demand as much as you can.


You may not control customer orders, but you can control how you release and schedule work internally. Aim for a smoother, more predictable intake.

3. Work in smaller batches.


Break large projects into smaller, independently valuable slices. This reduces the bullwhip effect and makes pull signals more meaningful.

4. Define and evolve standardized work.


Document the current best-known way to handle tasks in each stage. Keep it light, but explicit—and improve it regularly.

5. Treat problems as signals, not nuisances.


When the board shows bottlenecks or constant backflows, don’t hide them. Use them as starting points for problem‑solving.

6. Kaizen.


Kanban is not static. It’s a feedback system. Review your flow, experiment with changes, and keep learning.

Final Thoughts

Kanban is powerful precisely because it exposes reality. It doesn’t fix your processes; it reveals them. That revelation can feel like the sword’s edge cutting back toward the user.

If we:

• Ignore the need for leveled work,

• Attach Kanban to large, lumpy batches,

• Skip standardized work,

Tolerate unstable processes and high defects,

Then Kanban will hurt. Not because the method is wrong, but because it is doing its job of making our problems visible.

The next time you hear “Kanban doesn’t work here,” pause and ask a different question:

What problems has Kanban revealed that we haven’t been willing to solve yet?

That is usually where the real work begins.