TPS Relationships #6 — Heijunka & Kanban: Stability Makes Pull Possible
Heijunka and Kanban are often taught separately, but they depend deeply on one another. Heijunka creates the stability and rhythm that make replenishment signals meaningful, while Kanban connects that rhythm to actual consumption. Together, they help create a pull system that is both responsive and capable of revealing abnormalities.
TPS FUNDAMENTALSTPS RELATIONSHIPS
TPS Relationships #6 — Heijunka & Kanban: Stability Makes Pull Possible
Kanban is often described as a pull system.
That description is useful, but incomplete.
A Kanban card, container, empty space, electronic signal, or replenishment trigger does not create pull by itself.
It communicates that something has been consumed and needs to be replenished.
That distinction matters.
Because when Kanban is introduced as a stand-alone tool, organizations often expect the signal itself to create flow, reduce inventory, improve responsiveness, and stabilize production.
But a signal can only regulate a system that is sufficiently capable of responding to it.
This is where Heijunka and Kanban become deeply connected.
Heijunka helps distribute production volume and product mix more evenly over time.
It does not mean pretending that customer demand is perfectly stable.
It means avoiding the unnecessary amplification of variation inside the production system.
Customer demand may fluctuate.
But the production system does not necessarily need to reproduce every fluctuation immediately.
When every change in demand becomes a change in schedule, every urgent request becomes a priority, and every priority becomes a new production sequence, the system begins to oscillate.
Large batches appear.
Schedules are constantly revised.
Materials are expedited.
Queues grow.
People lose confidence in the plan.
And eventually, the organization starts compensating with more inventory, more supervision, more meetings, and more emergency decisions.
Kanban introduced into that environment may still function mechanically.
A card moves.
A bin becomes empty.
A signal is generated.
But the signal is now entering a system that may not be capable of responding predictably.
The result is important:
Kanban begins to transmit instability instead of regulating flow.
A replenishment signal says, in effect:
“Something was consumed. Please restore it.”
But if production priorities are changing constantly, setups are long, batch sizes are large, capacity is uneven, or upstream processes are unreliable, replenishment may not occur when expected.
More Kanban may then be added.
More inventory may be placed in the supermarket.
More safety stock may be introduced.
More exceptions may be created.
And slowly, the organization begins to conclude that “Kanban does not work here.”
The problem, however, may not be Kanban.
The problem may be the environment in which we are asking Kanban to operate.
That is why Heijunka matters.
By leveling volume and mix, Heijunka helps create a more repeatable rhythm.
It reduces the tendency to produce Monday’s demand on Monday, Tuesday’s demand on Tuesday, and react continuously to each short-term fluctuation.
Instead, production is organized around a more stable pattern that the system can reasonably sustain.
That stability changes the meaning of the Kanban signal.
Now, when something is consumed, the replenishment request enters a system with a more predictable workload.
Capacity has not suddenly been redirected.
The sequence has not been completely rewritten.
Production is not constantly being asked to switch from one extreme to another.
The signal becomes easier to trust.
And this is one of the most important relationships between Heijunka and Kanban:
Heijunka improves the environment in which Kanban can work.
But the relationship also works in the opposite direction.
Heijunka alone does not create pull.
A leveled production plan can still become a centrally controlled schedule pushed through the factory.
We can level the sequence beautifully and still tell every process exactly what to produce, when to produce it, and how much to produce.
That may create a more stable schedule.
But it does not necessarily create a self-regulating flow.
Kanban adds something different.
It connects actual consumption with replenishment.
What is taken creates permission to replace it.
That feedback loop prevents production from becoming completely detached from what is actually being used downstream.
In that sense:
Heijunka creates rhythm.
Kanban creates response.
Heijunka helps prevent the system from overreacting to variation.
Kanban helps prevent the system from producing without consumption.
One reduces unnecessary instability.
The other creates a disciplined feedback mechanism.
Together, they help the system regulate itself.
This is also why Kanban should not be confused with inventory control.
The visible card, bin, rack, or board is only the communication mechanism.
The deeper purpose is to establish clear rules for replenishment and limit the amount of work circulating through the system.
Similarly, Heijunka should not be reduced to a scheduling board.
The Heijunka box is only a representation.
The deeper purpose is to design a production rhythm that reduces unnecessary variation and makes abnormalities easier to see.
Both ideas point toward the same underlying principle:
A good production system should not need constant human intervention to decide what to do next.
The system should make the next action increasingly obvious.
Consumption creates a signal.
The signal requests replenishment.
The leveled rhythm creates the conditions in which replenishment can occur predictably.
And when that rhythm is disturbed, the disturbance becomes visible.
That visibility is critical.
Without stability, almost everything looks urgent.
When everything is changing constantly, it becomes difficult to distinguish normal variation from abnormal conditions.
But when the system has a rhythm, deviation becomes easier to see.
A late replenishment means something.
A missing Kanban means something.
A supermarket that repeatedly empties means something.
A process that cannot maintain the leveled sequence means something.
The relationship between Heijunka and Kanban therefore goes beyond material movement.
Together, they help the organization see the behavior of the system.
This is where their real value begins.
Because the objective is not to make Kanban cards move perfectly.
And the objective is not to protect the Heijunka schedule at all costs.
The objective is to create a system stable enough that abnormalities become visible, yet responsive enough that actual consumption continues to guide production.
This distinction is important.
Stability is not rigidity.
Heijunka is not about freezing the world.
Kanban is not about mechanically obeying cards regardless of circumstances.
Both are part of a learning system.
When demand changes structurally, the leveling pattern may need to change.
When replenishment repeatedly fails, Kanban quantities, process capability, lead time, reliability, or supermarket design may need to be reconsidered.
The system should not simply force reality to fit the tool.
The tool should help us understand reality better.
That may be the most useful way to think about their relationship.
Heijunka reduces noise.
Kanban transmits information.
And information becomes much more useful when the system is not constantly drowning it in noise.
A pull system therefore requires more than a signal.
It requires conditions that allow the signal to mean something.
Because pull needs a signal.
But a signal without stability can easily become noise.