Key takeaways
Short answer: Heijunka and kanban are complementary lean tools that are often confused because both relate to flow. Heijunka is about leveling — deliberately smoothing the volume and mix of production so you build a steady, repeating pattern instead of reacting to lumpy demand. Kanban is about signaling — pulling replenishment of exactly what was consumed. Heijunka decides the even rhythm of what to make; kanban feeds material to that rhythm. They are strongest together: kanban on top of a leveled schedule. For the pull side, see andon vs kanban and push vs pull production.
Heijunka is production leveling: deliberately smoothing both the volume and the mix of what you produce over a period, so the schedule becomes even and repeating rather than lumpy and reactive. Instead of building a huge batch of product A on Monday and scrambling for B on Friday because that is how orders arrived, heijunka distributes the work into a balanced, repeating pattern — a little of each, in a steady sequence, every day. The aim is to decouple the unevenness of customer demand from the production floor, so the line runs to a stable rhythm. That stability is what makes everything downstream — staffing, material flow, equipment load — predictable instead of chaotic.
Kanban is a pull signal: a card, bin, or electronic trigger that authorises producing or replenishing exactly what a downstream step has just consumed. When the next process takes a part, kanban tells the upstream process to make one to replace it — no more, no less. Kanban controls the flow of material and the level of in-process inventory, capping work in progress and tying production to real consumption. It is a beautifully simple feedback mechanism, but it has an important dependency: kanban regulates flow against whatever demand pattern it sees. If that demand pattern is wildly uneven, kanban faithfully transmits the chaos upstream rather than absorbing it.
The distinction is what each tool decides. Heijunka decides the pattern — the leveled volume and mix the plant will build, smoothing demand into a steady rhythm. Kanban decides the flow — when to replenish what was consumed, given that pattern. Heijunka is upstream of kanban in logic: it shapes the demand signal into something smooth, and kanban then pulls material to feed it. This is why they are not alternatives. Heijunka without kanban lacks the material-flow control to execute the level plan; kanban without heijunka pulls against lumpy demand and recreates the very unevenness lean is trying to remove. The pairing is the point.
Here is the dependency that trips teams up. Imagine demand that is genuinely spiky — calm for days, then a sudden surge. Run pure kanban against it and the pull signal transmits the spike straight upstream: the surge demands a burst of replenishment that overloads machines and people, forces frantic changeovers, and then collapses back to idle. The unevenness (mura) creates overburden (muri), and both create waste. Put heijunka first — level the spike into a smooth, repeating daily pattern, buffered appropriately — and kanban now pulls against a steady signal. The same pull mechanism that caused chaos against lumpy demand produces calm, predictable flow against a leveled one. Heijunka is what makes kanban safe.
A plant makes products A, B, and C. Weekly orders arrive lumpy: a big slug of A early, C late. Running kanban alone, the floor swings from an A marathon to a C scramble, with long changeovers and uneven load. Apply heijunka: convert the weekly mix into a smooth daily sequence — say A, B, C, A, B, C — repeated each day, so every product is built a little, every day, in a steady rhythm. Now the kanban loops pull material against that even pattern: smaller, frequent replenishments instead of huge erratic ones. Changeovers become routine and planned (rewarding any SMED work), machine load steadies, and inventory drops. Leveling set the rhythm; kanban fed it.
Both tools attack the unevenness and overburden that silently erode OEE. Lumpy, unleveled production drives panic changeovers, speed swings, and the micro-stops of a line lurching between extremes — all performance and availability losses. Heijunka's steady rhythm lets equipment run at a consistent, sustainable pace, which lifts the performance factor and makes losses legible. Kanban's WIP cap removes the overproduction waste that flatters utilisation while creating no value. Together they convert a chaotic, hard-to-measure operation into a steady one where the six big losses stand out clearly and OEE both rises and stabilises.
Fabrico measures whether a leveled, pulled operation is actually running as smoothly as intended. By tracking performance, micro-stops, and changeover-related losses shift by shift, it shows where unevenness is still costing OEE — the residual spikes a heijunka plan has not yet smoothed, or the changeover losses that leveling has made more frequent and SMED should target. That turns leveling and pull from principles into measured, improvable practice. Book a demo to see how evenly your lines really run.
Heijunka is production leveling — smoothing the volume and mix of what you build into a steady, repeating pattern. Kanban is a pull signal that authorises replenishing what was just consumed. Heijunka sets the even rhythm; kanban controls the material flow that feeds it.
Kanban works far better on top of a leveled schedule. Run against lumpy demand, pure kanban transmits the spikes upstream and causes overburden. Heijunka smooths the demand first, so kanban then pulls against a steady, manageable signal.
Heijunka is a Japanese lean term for production leveling. It means deliberately distributing production volume and product mix evenly over time, building a little of each product in a repeating sequence rather than large reactive batches.
It removes unevenness (mura) and the overburden (muri) it causes. By smoothing lumpy demand into a steady rhythm, it makes staffing, material flow, and equipment load predictable, and reduces the panic changeovers and stops that uneven production creates.
Both reduce the unevenness and overproduction that erode OEE. Heijunka's steady rhythm lifts the performance factor and makes losses visible; kanban's WIP cap removes overproduction waste. Together they raise and stabilise OEE.
Anmeldung
Blog
