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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
Purposedifferent
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.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.During an acute incident with several people involved, the method creates a clear leadership and communication structure. It reduces chaos when fast coordination and clean situational awareness are both needed at once.In preparing for rare incidents, the method tests response capability under controlled conditions. It shows where assumptions about stability, roles, and recovery are too optimistic.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
30-90 min1-3 hAs neededHalber Tag
Participantsdifferent
1-61-84-155-20
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Decision Tree, Option Map, Assumption ListArgument Map, Evidence Gaps, Decision RationaleIncident Log, Action Tracker, Stakeholder UpdatesSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
DecisionTreeOptions
SensemakingDecisionRationale
IncidentOperationsReliability
ResilienceOperationsIncident
Add more methods