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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree Analysis
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Purposedifferent
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 critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage.For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps.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
MediumHighHighLow
Timedifferent
1-3 h2-6 hMehrere Tage bis Wochen15-30 min
Participantsdifferent
3-103-82-62-6
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Process Map, Handoff List, Improvement BacklogFault Tree, Critical Paths, Cause Hypotheses, Control ActionsMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsRoot cause notes, Countermeasures
Tagsno overlap
ProcessOperationsImprovement
RiskRoot causeSafety
Root causeSafetySystemicIncident
Root causeIncidentLeanProblem solving
Add more methods