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 Dot Estimation.
Facilitation
Dot Estimation
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 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.
Complexitydifferent
MediumMediumLow
Timedifferent
10-30 min je ItemAs needed5-20 min
Participantsdifferent
1-84-153-20
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Three-Point Estimate, Risk Range, Assumption NotesIncident Log, Action Tracker, Stakeholder UpdatesEffort Heatmap, Risk Signals, Discussion Targets
Tagsno overlap
EstimationUncertaintyForecasting
IncidentOperationsReliability
EstimationEffortRisk
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for PERT Estimation.
Decision Making
PERT Estimation
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis