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 Ideal Days.
Agile
Ideal Days
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
Paper illustration for Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Root Cause Tree Analysis
Operations
Root Cause Tree Analysis
Purposedifferent
When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats.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.When size or effort can only be estimated roughly, Dot Estimation condenses the group's experience into a quick range. It turns individual contributions into a visible selection. The result is captured as an Effort Heatmap, Risk Signals, and Discussion Targets.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
LowMediumLowMedium
Timedifferent
15-60 min1-4 h5-20 min1-3 h
Participantsdifferent
2-93-83-202-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Ideal Day Estimates, Assumption Notes, Capacity CaveatsProblem Statement, Cause Hypotheses, Confirmed Causes, Action PlanEffort Heatmap, Risk Signals, Discussion TargetsCause Tree, Evidence Notes, Countermeasures
Tagsno overlap
EstimationEffortAgile
Root causeProblem solvingQualityIncident
EstimationEffortRisk
Root causeTreeIncidentQuality
Add more methods