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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Failure Scenario Analysis.
Engineering
Failure Scenario Analysis
Purposedifferent
Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 h20–45 min30-90 min1-3 h
Participantsdifferent
3-12Small cross-functional group1-63-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
System Map, Dependencies, Leverage PointsRisk list, Mitigation plan, Assumption logDecision Tree, Option Map, Assumption ListFailure Scenarios, Risk Notes, Control Gaps, Test and Response Actions
Tagsno overlap
Systems thinkingMappingBoundariesChange
RiskDecisionFailurePlanning
DecisionTreeOptions
FailureResilienceRisk
Add more methods