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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Purposedifferent
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 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.For a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
As needed30-90 min2-8 h1-3 h
Participantsdifferent
4-151-62-82-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesDecision Tree, Option Map, Assumption ListProblem Analysis, Decision Analysis, Risk PlanCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
IncidentOperationsReliability
DecisionTreeOptions
Problem solvingRoot causeDecisionOperations
Root causeTreeIncidentQuality
Add more methods