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 fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.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
MediumMediumLowMedium
Timedifferent
10-30 min je ItemAs needed30-60 min1-4 h
Participantsdifferent
1-84-152-83-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Three-Point Estimate, Risk Range, Assumption NotesIncident Log, Action Tracker, Stakeholder UpdatesFishbone Diagram, Cause Categories, Investigation BacklogProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
EstimationUncertaintyForecasting
IncidentOperationsReliability
Root causeQualityOperations
Root causeProblem solvingQualityIncident
Add more methods