methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.
Complexitydifferent
HighMediumLowLow
Timedifferent
2-6 h1-3 h30-120 min15-30 min
Participantsdifferent
3-103-102-62-6
Formatsame
WorkshopWorkshopWorkshopWorkshop
Outputdifferent
FMEA Table, Risk Priority, Mitigation ActionsProcess Map, Handoff List, Improvement BacklogObservation Notes, Improvement IdeasRoot cause notes, Countermeasures
Tagsno overlap
RiskQualityOperationsRoot cause
ProcessOperationsImprovement
LeanObservationProcessOperations
Root causeIncidentLeanProblem solving
Add more methods