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 Fault Tree Analysis.
Operations
Fault Tree Analysis
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Purposedifferent
For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.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.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.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.
Complexitydifferent
HighLowMediumHigh
Timedifferent
2-6 h30-120 min1-3 h2-6 h
Participantsdifferent
3-82-63-103-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsObservation Notes, Improvement IdeasProcess Map, Handoff List, Improvement BacklogFMEA Table, Risk Priority, Mitigation Actions
Tagsno overlap
RiskRoot causeSafety
LeanObservationProcessOperations
ProcessOperationsImprovement
RiskQualityOperationsRoot cause
Add more methods