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
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration of Barrier Analysis with its method-specific working model.
Operations
Barrier Analysis
Paper illustration for Fault Tree Analysis.
Operations
Fault Tree 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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.For a risk that can only be managed through multiple layers of protection, the method examines the effectiveness of each barrier. It shows where safeguards are missing, too weak, or fail under real conditions.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.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
1-3 h45-90 min2-4 h2-6 h
Participantsdifferent
3-122-82-63-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
System Map, Dependencies, Leverage PointsAssumption List, Critical Assumptions, Learning PlanBarrier Inventory, Failure Analysis per Barrier, Action BacklogFault Tree, Critical Paths, Cause Hypotheses, Control Actions
Tagsno overlap
Systems thinkingMappingBoundariesChange
AssumptionsRiskDecisionDiscovery
Root causeSafetyIncident
RiskRoot causeSafety
Add more methods