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 Three-Point Estimation.
Decision Making
Three-Point Estimation
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Kepner-Tregoe
Operations
Kepner-Tregoe
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Purposedifferent
A single estimate for effort, time, or risk often looks too smooth for the real uncertainty behind it. It separates options, evaluation criteria, and open risks. The result is captured as a Three-Point Estimate, Risk Range, and Assumption Notes.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 a disturbance that's hard to pin down, the method cleanly separates problem, cause, and decision. It reduces mixing when symptoms allow several interpretations.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
10-30 min je ItemAs needed2-8 h1-4 h
Participantsdifferent
1-84-152-83-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Three-Point Estimate, Risk Range, Assumption NotesIncident Log, Action Tracker, Stakeholder UpdatesProblem Analysis, Decision Analysis, Risk PlanProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
EstimationUncertaintyForecasting
IncidentOperationsReliability
Problem solvingRoot causeDecisionOperations
Root causeProblem solvingQualityIncident
Add more methods