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
Paper illustration for Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Purposedifferent
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.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 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.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.
Complexitydifferent
HighMediumLowMedium
Timedifferent
0.5-3 TageAs needed20-60 min60-180 min
Participantsdifferent
5-154-151-44-20
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop
Outputdifferent
Rich Picture, Root Definitions, Conceptual Models, Change AgendaIncident Log, Action Tracker, Stakeholder UpdatesRunbook, Checklist, Escalation PathCynefin Map, Domain-specific Actions, Sensemaking Notes
Tagsno overlap
Soft systemsComplexitySensemakingSystems thinking
IncidentOperationsReliability
OperationsReliabilityDocumentation
ComplexitySensemakingDecision
Add more methods