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
A3 Problem-Solving workspace showing the question, observations, and next decision.
Operations
A3 Problem Solving
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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.For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together.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
HighMediumMedium
Timedifferent
0.5-3 Tage45-90 minAs needed
Participantsdifferent
5-152-54-15
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Rich Picture, Root Definitions, Conceptual Models, Change AgendaA3 Report, Action Plan, Root Cause AnalysisIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
Soft systemsComplexitySensemakingSystems thinking
LeanProblem solvingCoachingOperations
IncidentOperationsReliability
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop