The 8 Wastes

Mura

Unevenness in flow. The waste that creates the other two.

Updated
·
4
min read
Definition

What is Mura?

Mura is the Japanese lean term for unevenness or variation in flow. It is one of the 3Ms (muda, mura, muri) and is often the root cause of the other two: mura forces operators to alternate between rushed periods (creating muri, overburden) and slow periods (creating muda, waste). Heijunka, production leveling, is the standard countermeasure.

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."

How mura works

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.

Where mura shows up on a small shop floor

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.

Common mistakes with mura

  • Blaming customer demand. Most mura is internal scheduling, not customer behavior. Look in the mirror before looking at the order book.
  • Leveling by stockpiling. Building inventory to smooth output is hiding mura, not removing it. Real heijunka levels the production schedule.
  • Treating each spike as a one-off. If you're firefighting once a week, that pattern is mura, not bad luck.
  • Optimizing each station independently. Local optimization creates global mura. The pacemaker process should set the beat; everything else flows to it.
  • Ignoring mura because mura wastes feel like normal manufacturing. Heroic Fridays look like commitment. They're a system failure.

Mura and related Lean tools

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.

Common questions

The questions we hear most about this term.

How is Mura different from Muri?
Mura and muri are linked but distinct. Mura is unevenness: demand spikes and lulls, batch processing that creates feast-and-famine for downstream stations, schedules that mix easy and hard jobs unpredictably. Muri is overburden: people or equipment pushed beyond reasonable capacity. Mura causes muri. When work arrives in lumpy bursts, operators get overburdened during the burst (muri) and underused during the lull (muda). Smoothing mura usually relieves muri without any other change.
Is Mura the same as variation in Six Sigma?
Closely related but framed differently. Six Sigma's variation is statistical: how much a measurement (part dimension, cycle time) deviates from its mean. Mura is operational: how much the actual flow of work bounces around what a steady process would look like. Six Sigma reduces variation in a process by tightening it; lean reduces mura by smoothing the demand or production schedule. Both are useful; they live in different parts of the improvement toolkit.
When should I attack Mura first instead of Muda?
When the shop is constantly switching between rush and idle, even though average demand is reasonable. A shop where some days are heroic 12-hour pushes and others are 6 hours of cleaning has a mura problem. Heijunka (production leveling) usually solves it. If you attack muda in a mura-plagued shop, the muda comes back as soon as the next rush starts. Mura first, then muda lives under control.
What are common mistakes when addressing Mura?
The biggest is assuming mura comes from customer demand, when most of it is self-inflicted. Internal scheduling decisions, batch sizing, hot-order expediting, and changing priorities create more mura than actual customer behavior. The second is "leveling" by accumulating finished goods inventory to absorb the spikes, which just hides mura under excess inventory. Real heijunka levels production by leveling actual work, not by burying it.
How does Mura look on a small shop floor?
As stress. The Monday meeting is always about how behind we are. By Thursday everyone is staying late. Friday is half a day because the shipments are out. Then Monday starts over because next week's orders have stacked up over the weekend. The week-over-week pattern is mura. The lean countermeasure is leveling the schedule across the week, not running heroic catch-ups every Friday.

Ditch the whiteboards and spreadsheets.

Same-day setup. No distributor lock-in. Zero stockouts. Top teams double revenue in 9 months.