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 for Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Game Day workspace showing the question, observations, and next decision.
DevOps
Game Day
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.Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.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
MediumMediumHighHigh
Timedifferent
As needed60-180 min0.5-3 TageHalber Tag
Participantsdifferent
4-154-205-155-20
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesCynefin Map, Domain-specific Actions, Sensemaking NotesRich Picture, Root Definitions, Conceptual Models, Change AgendaSimulation Notes, Gaps List, Updated Runbooks
Tagsno overlap
IncidentOperationsReliability
ComplexitySensemakingDecision
Soft systemsComplexitySensemakingSystems thinking
ResilienceOperationsIncident
Add more methods