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
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field 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.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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.
Complexitydifferent
HighLowLow
Timedifferent
2-6 h15-30 min45-90 min
Participantsdifferent
3-82-63-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsRoot cause notes, CountermeasuresForce Field Map, Change Levers, Risk Notes
Tagsno overlap
RiskRoot causeSafety
Root causeIncidentLeanProblem solving
ChangeDecisionStrategy
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration of MORT Analysis with its method-specific working model.
Operations
MORT Analysis
Paper illustration for OODA Loop.
Decision Making
OODA Loop