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 Dot Estimation.
Facilitation
Dot Estimation
Paper illustration for Ideal Days.
Agile
Ideal Days
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Purposedifferent
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.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.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.After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures.
Complexitydifferent
LowLowMediumMedium
Timedifferent
5-20 min15-60 minAs needed30-90 min
Participantsdifferent
3-202-94-153-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Effort Heatmap, Risk Signals, Discussion TargetsIdeal Day Estimates, Assumption Notes, Capacity CaveatsIncident Log, Action Tracker, Stakeholder UpdatesPostmortem Doc, Action Items, Timeline
Tagsno overlap
EstimationEffortRisk
EstimationEffortAgile
IncidentOperationsReliability
Site Reliability EngineeringIncidentLearningReliability
Add more methods