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
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
Paper illustration for Three-Point Estimation.
Decision Making
Three-Point Estimation
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
For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access.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.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
LowMediumMediumMedium
Timedifferent
20-60 min10-30 min je ItemAs needed30-90 min
Participantsdifferent
1-41-84-153-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathThree-Point Estimate, Risk Range, Assumption NotesIncident Log, Action Tracker, Stakeholder UpdatesPostmortem Doc, Action Items, Timeline
Tagsno overlap
OperationsReliabilityDocumentation
EstimationUncertaintyForecasting
IncidentOperationsReliability
Site Reliability EngineeringIncidentLearningReliability
Add more methods