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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.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.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.
Complexitydifferent
LowHighMediumMedium
Timedifferent
20-60 min0.5-3 Tage60-180 minAs needed
Participantsdifferent
1-45-154-204-15
Formatdifferent
AsyncWorkshopWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathRich Picture, Root Definitions, Conceptual Models, Change AgendaCynefin Map, Domain-specific Actions, Sensemaking NotesIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
OperationsReliabilityDocumentation
Soft systemsComplexitySensemakingSystems thinking
ComplexitySensemakingDecision
IncidentOperationsReliability
Add more methods