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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper matrix with six colored hat cards for information, feeling, value, caution, ideas and process control.
Facilitation
Six Thinking Hats
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.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.When a topic gets stuck too quickly in the same thinking mode, Six Thinking Hats deliberately separates the perspectives. This means facts, risks, creativity, and emotional signals get worked through one after another instead of mixed 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
LowMediumMediumMedium
Timedifferent
20-60 min30-90 min45-90 minAs needed
Participantsdifferent
1-41-64-124-15
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathDecision Tree, Option Map, Assumption ListPerspective Notes, Decision Inputs, Action ItemsIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
OperationsReliabilityDocumentation
DecisionTreeOptions
FacilitationOptionsDecision
IncidentOperationsReliability
Add more methods