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 CATWOE Analysis.
Systems Thinking
CATWOE Analysis
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Purposedifferent
CATWOE structures a problem from six viewpoints and prevents too narrow a view of the situation. Different experiences of the system become comparably discussable this way.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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
45-90 min60-180 min30-90 minAs needed
Participantsdifferent
3-84-203-124-15
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
CATWOE Canvas, Root Definition, Stakeholder Perspectives, ConstraintsCynefin Map, Domain-specific Actions, Sensemaking NotesPostmortem Doc, Action Items, TimelineIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
Systems thinkingFramingStakeholders
ComplexitySensemakingDecision
Site Reliability EngineeringIncidentLearningReliability
IncidentOperationsReliability
Add more methods