The 8 Wastes

Muri

Overburdening people or equipment. The hidden cost of pushing too hard.

Updated
·
4
min read
Definition

What is Muri?

Muri is the Japanese lean term for overburden of people or equipment. It is one of the 3Ms (muda, mura, muri). Muri occurs when work, equipment, or operators are pushed beyond reasonable capacity, which creates fatigue, breakdowns, defects, and turnover. Most muri is caused by mura (unevenness), so heijunka and production leveling are the upstream countermeasures.

Muri is the lean concept of overburden. It is one of the 3Ms alongside muda and mura, and it tends to appear in the middle of the chain: mura (unevenness) creates muri (overburden), which produces muda (waste). The diagnostic value of muri is that it shows up before the waste does. If you can see muri early, you can prevent the muda that's coming next.

"Muri is the warning shot. Muda is the wound."

How muri works

Muri shows up in three forms: muri on people, muri on equipment, and muri on processes. Muri on people is the most familiar: operators pushed to work longer shifts, faster cycles, or with less recovery than is sustainable. The first signs are fatigue, error rates, and minor injuries. The later signs are turnover and serious accidents. Muri on people is also the easiest to hide, because most workers will accept short-term overburden if they trust it's temporary.

Muri on equipment is mechanical. A press run beyond its rated cycle rate generates heat, vibration, and tool wear. A conveyor loaded beyond its rated capacity sags and develops bearing problems. A CNC machine run without scheduled preventive maintenance because the shop "can't afford the downtime" eventually delivers a much longer breakdown. Muri on equipment is what makes mean-time-between-failures shorter than the spec sheet.

Muri on processes is more subtle. A process designed for steady-state production but run in irregular bursts will produce defects during the burst. A quality gate sized for normal flow will miss defects when the flow surges. A planning system designed for monthly horizons will produce bad plans when forced into weekly cycles. The process itself is being overburdened beyond what its design can handle.

In all three cases, the root cause is usually mura. The shop has uneven flow, the uneven flow creates peaks, the peaks overburden whoever or whatever is on the peak. Adding capacity is the wrong fix; it just makes the peaks bigger. The right fix is leveling the flow with heijunka, which lowers the peak height to within sustainable capacity.

Where muri shows up on a small shop floor

Imagine a 28-person CNC shop running parts for medical-device customers. Demand looks steady on the monthly report. Internally, the schedule is being adjusted weekly based on which customer is calling, so the actual work pattern in the shop bounces hard between programs. One week is 80 percent of the work on the main mill running a tight tolerance program; the next week is 20 percent on the main mill and 80 percent split across the other three machines.

The visible problems: the main mill operator quit last quarter. Defect rates on the tight-tolerance program spiked 4 weeks before the resignation. The main mill itself is showing chatter that wasn't there last year. The shop owner has been blaming the operator's attention to detail.

A muri diagnosis would reframe. The operator was being asked to run an 80-percent-utilized machine on the toughest program in the shop with no real backup. The chatter is the machine telling you it's overburdened. The defects were the early warning. The resignation was the operator finishing the message the defects started. None of this is the operator's fault. The shop was running on muri.

The fix is upstream. Level the program mix across weeks so the main mill isn't 80 percent loaded one week and 20 percent the next. Cross-train a second operator on the main mill so the load can be split. Add a scheduled maintenance window so the chatter gets resolved before it becomes a breakdown. None of these changes need more capacity. They use the existing capacity more sustainably.

Common mistakes with muri

  • Buying capacity to absorb the overburden. Adding people or machines to a mura-plagued shop makes the peaks bigger, not smaller.
  • Treating it as a workforce issue. Muri is what the system is asking of the workforce. Train the system, not the workers.
  • Hiding it under "we're just busy." Sustained busy is muri. Real busy is even and recoverable.
  • Ignoring early signs in equipment. Vibration, chatter, heat, oil-color changes are equipment muri. They precede breakdowns by weeks or months.
  • Solving it with overtime. Overtime is muri being paid for in cash. The cash doesn't fix the cause.

Muri and related Lean tools

Muri is one of the 3Ms and is usually downstream of mura. Its primary countermeasure is heijunka, production leveling, which reduces the peaks that create overburden. On the equipment side, total productive maintenance is the discipline that prevents muri on machines from becoming muda through breakdowns.

Common questions

The questions we hear most about this term.

How is Muri different from Mura?
Mura is unevenness. Muri is overburden. They are linked: when work arrives unevenly (mura), the high points overburden people and equipment (muri), and the low points create waste (muda). Most muri comes from upstream mura, so addressing the unevenness usually reduces the overburden without needing to add capacity. A shop that thinks it has a muri problem usually has a mura problem.
Is Muri the same as overwork?
Related but not identical. Overwork usually means hours-per-week of human labor. Muri includes that but also covers equipment running beyond reasonable speed, processes running beyond their stable capability, and supply chains pushed beyond their planned cadence. Muri on a machine looks like vibration, heat, drift. Muri on a person looks like errors, injuries, and quits. Both shorten the life of the resource and reduce output.
When does Muri show up before Muda?
In a shop with chronic mura. When the wave hits, operators sprint and machines run hot. That's muri appearing before any obvious muda. The muda comes later: errors made during the sprint, downtime from the overheated machine, turnover from the burned-out operator, rework from the defects shipped during the rush. Spotting muri during the wave gives you the earliest warning that mura is creating waste downstream.
What are common mistakes when addressing Muri?
The biggest is hiring more people or buying more equipment to absorb the overburden, when the right move is leveling the demand that's creating it. Adding capacity to a mura-plagued shop just makes the spikes bigger. The second mistake is treating muri as a workforce HR issue (more training, more support) when the system is asking for more than the workforce can sustainably give. Address the load, not the person.
How does Muri look on a small shop floor?
Quiet at first. Operators don't complain. Machines don't refuse to run. Then the pattern: rising defect rates after long shifts. Maintenance calls clustered on Friday afternoons. The same skilled operator working the same machine for 6 weeks straight because no one else is trained on it. Turnover spiking in the same department three quarters in a row. Muri is a slow leak. By the time it's visible, it's been costing for months.

Ditch the whiteboards and spreadsheets.

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