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
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Change Analysis.
Operations
Change 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.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.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.
Complexitydifferent
HighLowMediumMedium
Timedifferent
2-6 h45-90 min15-60 min je Zyklus45-120 min
Participantsdifferent
3-83-121-82-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Fault Tree, Critical Paths, Cause Hypotheses, Control ActionsForce Field Map, Change Levers, Risk NotesSituation Assessment, Decision Loop, Action UpdatesChange Matrix, Cause Hypotheses, Validation Questions, Action List
Tagsno overlap
RiskRoot causeSafety
ChangeDecisionStrategy
DecisionChangeLearningStrategy
ChangeRoot causeTroubleshootingComparison
Add more methods