For a process that keeps people busy but creates little value, the method exposes waste. It directs attention to unnecessary movement, waiting times, rework, and overdelivery.
Operations Analysis method
Waste Analysis
Identifies waste along a process, prioritises impact, and derives improvements.
The flow is read along its value creation so wasteful activities can be distinguished from the actual contribution. Friction and detours become structural signals rather than individual blame. The analysis provides a basis for reducing effort while protecting quality.
Which work creates customer value, which waste is immediately avoidable, which is currently necessary, and which unevenness or overburden produces it?
- Participants
- 2-8
- Time
- 60–120 minutes for a bounded value stream; add gemba observation.
The steps form one complete method run.

Value
Value criterion
Define customer, outcome, and conditions under which an activity creates value.
Observe
Observed flow
Capture steps, times, paths, inventory, interruptions, and strain in actual flow.
Classify
Waste register
Classify non-value work as Muda type 1 or 2, unevenness as Mura, and overburden as Muri.
Prioritise
Priority
Assess risk, frequency, time, and relationships; choose system cause rather than visible symptom.
Test
Improvement test
Run a small countermeasure with prediction, owner, guardrails, and review.
Add new evidence at review and version decisions with the prior state.
A good fit when
Bei einem Prozess, der viel beschäftigt, aber wenig Wert schafft, legt die Methode Verschwendung offen. Sie richtet den Blick auf unnötige Wege, Wartezeiten, Nacharbeit und Übererfüllung.
Ideal for
- Lean process improvement
- Lead time reduction
- Operational efficiency
Not good for
- Problems without process visibility
- Pure creative work
- Unclear customer value definition
Outputs

Improvement test
Waste register with value relation, Muda type 1/2, Mura, Muri, evidence, cause, and prioritised experiment.
Waste Analysis · working structure
Fictional example
Fictional values show the actual method fields.
| Activity | Evidence | Muda | Mura | Muri | Cause | Test |
|---|---|---|---|---|---|---|
| Unit searchAdd evidence and rationale. | avg 7 min; 94m walk | Type 2 | worse with slot clustering | lifting under time pressure | no presorting | pilot slot cart |
| Safety checkAdd evidence and rationale. | 1.8 min; legally required | Type 1 | stable | none | mandatory control | retain |
1. Evidence
- Unit search
- avg 7 min; 94m walk
- Safety check
- 1.8 min; legally required
2. Muda
- Unit search
- Type 2
- Safety check
- Type 1
3. Mura
- Unit search
- worse with slot clustering
- Safety check
- stable
4. Muri
- Unit search
- lifting under time pressure
- Safety check
- none
5. Cause
- Unit search
- no presorting
- Safety check
- mandatory control
6. Test
- Unit search
- pilot slot cart
- Safety check
- retain
All values are fictional.
First step
Set one concrete value stream, customer, and desired outcome; observe actual work at gemba.
Good to do first
Deep dive
The workflow is read along its value creation, so useless activities are clearly separated from the actual contribution. This makes friction and detours appear as a structural problem rather than individual failure. The analysis provides the basis for noticeably reducing effort without losing quality.
Waste Analysis uses the Lean idea that not every activity creates value for the customer. The method looks at process steps through categories such as transport, inventory, motion, waiting, overproduction, overprocessing, defects, and unused talent. That makes costs, delays, and quality problems tangible. The patterns lead to concrete improvement ideas for flow and quality.
Work close to the real process and use observable examples instead of abstract accusations. Treat the waste categories as a search aid, not as dogma. Finish by prioritizing a few improvements with high impact and a clear owner.
The method guide walks execution through 5 phases, timing, 5 pitfalls, and clear stop criteria.
Open method guideYour perspective
Does this method help with your work?
Your feedback helps shape the next improvements to methodatlas.
Sources and topics
Waste Analysis: WorksheetSet subject, evidence, roles, flow, and review.markdown
waste-analysis-working-template.md
Set subject, evidence, roles, flow, and review.
Waste Analysis: Worksheet
Question
To be confirmed
Desired outcome
To be confirmed
Scope
Complete run Time: 60–120 minutes for a bounded value stream; add gemba observation.
Complete this worksheet on paper or in your own document during the work.
Preparation for this scope
Method setup
- Materials: Customer value, observed process, time/motion/inventory data, Muda-Mura-Muri matrix, and action log
- Roles: Frontline team · process/value-stream owner · customer perspective · facilitator · action owners
- Advance information: Set one concrete value stream, customer, and desired outcome; observe actual work at gemba.
- Overall time needed: 60–120 minutes for a bounded value stream; add gemba observation.
- Setup: Prepare a workspace with Value · Observe · Classify · Prioritise · Test; separate example from live data.
Prepare for the work steps
Value: Value criterion
- Set one concrete value stream, customer, and desired outcome; observe actual work at gemba.
- Customer value, observed process, time/motion/inventory data, Muda-Mura-Muri matrix, and action log
Observe: Observed flow
- Value criterion
Classify: Waste register
- Observed flow
Prioritise: Priority
- Waste register
Test: Improvement test
- Priority
Waste Analysis · working structure
| Activity | Evidence | Muda | Mura | Muri | Cause | Test |
|---|---|---|---|---|---|---|
| Unit search | ||||||
| Safety check |
- Unit search: Add evidence and rationale.
- Safety check: Add evidence and rationale.
The blank worksheet contains prompts only.
Reference · original teaching example
Value: Value criterion
Expected artifact: Value criterion
Define customer, outcome, and conditions under which an activity creates value.
Entry:
...
- Is value defined by the recipient rather than internal utilisation?
Observe: Observed flow
Expected artifact: Observed flow
Capture steps, times, paths, inventory, interruptions, and strain in actual flow.
Entry:
...
- Were data gathered directly over several cases?
Classify: Waste register
Expected artifact: Waste register
Classify non-value work as Muda type 1 or 2, unevenness as Mura, and overburden as Muri.
Entry:
...
- Is every classification evidenced by concrete behaviour and effect?
Prioritise: Priority
Expected artifact: Priority
Assess risk, frequency, time, and relationships; choose system cause rather than visible symptom.
Entry:
...
- Does priority address customer effect and system cause?
Test: Improvement test
Expected artifact: Improvement test
Run a small countermeasure with prediction, owner, guardrails, and review.
Entry:
...
- Does the test reduce waste without new Mura or Muri?
Open questions and next steps
...
Method guide: https://methodatlas.meierhoff-systems.de/en/methods/waste-analysis/run-sheet
Alternatives and neighbors
Fitting alternatives with decision guidance, followed by other related methods.

Instead of Waste Analysis, choose Process Mapping when you want to document a workflow step by step and make handoffs visible.

Instead of Waste Analysis, choose Standard Work Analysis when you want to precisely standardize and stabilize a proven way of working.

Condenses problem, analysis, countermeasures, and follow-up onto one sheet and forces joint analysis.

Runs changes as a repeatable cycle of Plan, Do, Check, and Act until a standard becomes solid.

Makes status, exceptions, and signals recognizable at a glance so teams can react faster.

Asks its way step by step to a controllable cause and stops only once an effective countermeasure is within reach.
Constraints and origin
Profile
- Method form
- Analysis method
- Participants
- 2-8
- Time
- 45-120 min
- Maturity
- Canonical
- Origin
- Lean Community


