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
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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.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.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.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
As needed60-180 min45-90 min1-3 h
Participantsdifferent
4-154-202-81-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesCynefin Map, Domain-specific Actions, Sensemaking NotesAssumption List, Critical Assumptions, Learning PlanArgument Map, Evidence Gaps, Decision Rationale
Tagsno overlap
IncidentOperationsReliability
ComplexitySensemakingDecision
AssumptionsRiskDecisionDiscovery
SensemakingDecisionRationale
Add more methods