Muda, mura and muri reinforce each other

Muda, mura and muri reinforce each other

A weekly release surge can make people hurry, create errors and leave others waiting later. Those are connected observations, not three unrelated improvement projects. Ask how work arrives, what capacity is available, and where the method demands unreasonable effort. Then redesign the release or work arrangement with the people affected. A short pause may protect reliability; eliminating it without understanding the system can worsen the outcome. Compare customer service, workload and quality after the change. The aim is an easier, steadier method that removes avoidable waste without transferring burden elsewhere.

Follow the method

1. Unevenness
2. Overburden
3. Waste
4. Redesign and test

Show how a release surge becomes a queue

Fictional training case: a service coordinator receives 20 complete requests each weekday. An internal manager releases work to the processing team in one large Friday bundle. Analyst Luis asks whether overtime reflects customer demand, the release rule or a lack of capacity.

Follow the method

1. Mura
2. Muri risk
3. Muda candidates
4. Prediction

Friday is overloaded before the work begins

Use daily release and workload evidence to explain how unevenness can produce overburden and waste, then design a test without assuming that all quiet time is removable.

Fictional training case: a service coordinator receives 20 complete requests each weekday. An internal manager releases work to the processing team in one large Friday bundle. Analyst Luis asks whether overtime reflects customer demand, the release rule or a lack of capacity.

Role: Service team leader and request-release owner.

Normal condition

The team works at a sustainable pace and completes accepted requests accurately within the service promise.

The gap

The weekly total looks manageable, but a Friday surge produces repeated clarification calls and rushed corrections.

• Use the supplied daily sustainable processing capacity of 25 requests.
• This first-pass calculation ignores carry-in backlog and variation; verify both before implementing a release change.

1. Separate demand from the release rule

   Luis plots arrivals and released requests on the same five-day axis. Both total 100, but arrivals are steady and the internal release is concentrated on Friday.

   Why: The weekly sum hides the timing mechanism. A demand surge and a management-created release surge require different investigations.

   Evidence: Arrivals: 20 each day; release: 0, 0, 0, 0, 100.

2. Name each mechanism using evidence

   The release pattern is unevenness, or mura. Attempting 100 requests against a sustainable 25-request day is an overburden risk, or muri. Correction and repeat clarification are observed candidates for waste, or muda.

   Why: The labels describe linked conditions rather than three boxes into which each person must be placed. Do not diagnose worker effort from a chart.

   Evidence: The supplied Friday release is four times the declared daily sustainable capacity.

3. Keep the capacity assumption visible

   At the supplied limit, only 25 of the Friday release can be processed that day, leaving 75. Luis records that overtime results and actual quality rates have not been supplied.

   Why: A simple queue calculation can expose an impossible promise but cannot prove a medical, ergonomic or capability threshold. The declared capacity is a teaching assumption.

   Evidence: First-pass Friday remainder: 100 minus 25 = 75 requests.

4. Test a steadier release with safeguards

   The release owner proposes 20 complete requests daily, retaining necessary readiness checks. The team verifies that the information is available and the service promise allows immediate release.

   Why: Leveling a controllable internal release may reduce induced overload. It does not mean holding urgent customer work to make a graph smooth.

   Evidence: Proposed daily load 20 versus capacity 25; five-request nominal margin, not guaranteed spare capacity.

5. Check all three conditions after the trial

   Record waiting, repeat work, completion accuracy and experienced workload. Keep time for problem solving and response coverage rather than filling every quiet minute with more starts.

   Why: Removing visible idle time can remove the ability to absorb normal variation and then recreate overload elsewhere.

   Evidence: Trial review compares daily patterns, queues and worker feedback with the original mechanism.

The customer actually sends a Friday surge

A new observation shows 80 requests arrive on Friday and only five on each earlier weekday.

Reopen the demand and capacity assumptions; do not pretend the release manager created all the unevenness.

The same visual symptom can have a different cause. Options may include agreed lead times, flexible trained capacity or readiness changes, subject to customer needs.

Separate arrival and release histories support the revised explanation.

Run a practice session

Materials

• Five day cards and 60 request counters
• Release/arrival chart and queue worksheet

1. Compare the two patterns · 4 minutes

   What does the weekly total hide?

2. Build the Friday queue · 7 minutes

   Which assumption makes the 75-request remainder valid?

3. Calculate the warranty variant · 9 minutes

   Where does Thursday begin: zero or Wednesday’s remainder?

4. Plan transfer · 5 minutes

   What evidence would identify real demand variation?

Debrief

• Challenge claims that the team simply needs to work faster.
• Discuss necessary response capacity before eliminating apparent quiet time.

Use a separate row for arrivals, release, completion and queue; explain each change before viewing the solution.

Transfer into the work

Owner: Release owner with service team leader

Record: Daily arrivals/releases/completions, queue age and workload observations

Review: Daily during a limited trial, then at the agreed service review

Evidence: Accurate completion with less induced waiting and no increase in strain or hidden work

Review readiness, real demand variability and trained capacity; retain explicit urgent-work rules.