Unevenness in flow. The waste that creates the other two.
Mura is the lean concept of unevenness in flow. It is one of the 3Ms alongside muda and muri, and lean practitioners often treat it as the root M because it tends to generate the other two. A shop with mura swings between rushed bursts (which create overburden) and idle troughs (which create waste). Smoothing the unevenness usually relieves the other two wastes without further intervention.
"Mura is the wave. Muri is the cresting. Muda is the wreckage after the wave breaks."
Mura shows up in two places: in demand entering the shop, and in flow inside the shop. Demand-side mura is the natural variation in customer orders: more in March, less in July. Most shops can't directly control demand, but they can buffer it: smooth-the-output-by-leveling-the-input. That is what heijunka does.
Flow-side mura is the unevenness inside the shop, almost all of which is self-inflicted. Big batch sizes create feast-and-famine for the next station. Expediting hot orders disrupts steady-state production. Releasing all the week's work on Monday creates a wave that smooths into Wednesday and runs out by Thursday. Scheduling all easy jobs first to "build momentum" leaves the hard jobs piled up at the end of the week. Each of these is a decision that creates mura.
The mura-to-muri-to-muda chain is the reason lean treats mura as a top priority. When work arrives in waves, operators alternate between sprinting and waiting. The sprinting is muri: overburdened people, overheated equipment, rushed quality. The waiting is muda: idle time, premature setups to "stay busy," meetings that fill the gaps. Both wastes go away when the wave is flattened.
The standard countermeasure for mura is production leveling. At its simplest, leveling means scheduling each shift to do roughly the same volume and the same mix of products, rather than batching the week's orders into front-loaded runs. The heijunka box is the canonical physical artifact: a slotted board where each slot holds the kanban for one pitch of one product type, sequenced so the day's mix is evenly distributed across the shift.
Imagine a 30-person packaging shop running orders for three regional food brands. The owner has been working 60-hour weeks because every Friday is a scramble to ship. The Monday volume report shows the orders are actually steady week to week. The pattern that emerges from a waste walk: orders are released to the floor every Monday morning in a single batch. The production schedule sorts them by customer rather than by complexity. The shop runs the easy customer's jobs first because they're profitable per minute, leaving the harder customer's jobs piled up for Wednesday and Thursday, which then need overtime to ship by Friday.
This is pure mura. Demand is even. Output target is even. But the internal sequencing creates a wave: easy work fast on Mondays, hard work slow on Thursdays. The fix is not more capacity; it is leveling the schedule. Release each day's work as one-fifth of the week's mix instead of releasing the full week's batch on Monday. Sequence each day's work as a balanced rotation across all three customers rather than running one to completion before starting the next.
Within a month, the Friday scramble is gone. Operators are working steady eight-hour shifts. The same volume ships in the same week with less stress and less overtime. The shop didn't add capacity; it removed self-inflicted mura.
Mura is one of the 3Ms, paired with muda and muri. Its primary countermeasure is heijunka, production leveling, often implemented with a heijunka box. At a system level, mura is reduced by establishing a pacemaker process that sets a steady rhythm everything else aligns to.
The questions we hear most about this term.
Long-form guides that pick up where this definition leaves off, written for manufacturers running Arda today.
Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.