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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Purposedifferent
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.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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
As needed30-90 min60-180 min1-3 h
Participantsdifferent
4-151-64-201-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesDecision Tree, Option Map, Assumption ListCynefin Map, Domain-specific Actions, Sensemaking NotesArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
IncidentOperationsReliability
DecisionTreeOptions
ComplexitySensemakingDecision
SensemakingDecisionRationale
Add more methods