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 of System Dynamics Simulation with its method-specific working model.
Systems Thinking
System Dynamics Simulation
Stock and Flow Diagram method illustration showing its working structure
Systems Thinking
Stock and Flow Diagram
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
System Dynamics Simulation makes assumptions about time, delay, and feedback testable through experiments. It draws relationships, patterns, and feedback loops. The result is captured as a simulation model and scenario reports.A Stock and Flow Diagram shows how stocks, inflows, and outflows shape a system over time. It is especially suited when growth, delays, or capacity limits determine the dynamics.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
HighHighHighLow
Timedifferent
Mehrere Tage bis Wochen2-6 hMehrere Tage bis Wochen15-30 min
Participantsdifferent
1-5 Modellierende, Stakeholder asynchron1-62-62-6
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Simulation Model, Scenario ReportsStock and Flow Model, Dynamics Notes, Simulation HypothesesMORT Worksheets, Findings per Branch, Corrective Actions, Systemic RecommendationsRoot cause notes, Countermeasures
Tagsno overlap
Systems thinkingDynamicsSimulationAnalysis
DynamicsSimulationFeedbackSystems thinking
Root causeSafetySystemicIncident
Root causeIncidentLeanProblem solving
Add more methods