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 of ICE Scoring with its method-specific working model.
Product Strategy
ICE Scoring
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.When ideas need sorting quickly, it condenses impact, confidence, and effort into one compact score. It connects customer value, product logic, and decision priorities. The result is captured as an ICE table and top-ideas list.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
20-60 min30-60 minAs needed30-90 min
Participantsdifferent
1-42-84-153-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Runbook, Checklist, Escalation PathICE Table, Top Idea ListIncident Log, Action Tracker, Stakeholder UpdatesPostmortem Doc, Action Items, Timeline
Tagsno overlap
OperationsReliabilityDocumentation
PrioritizationScoringGrowthDecision
IncidentOperationsReliability
Site Reliability EngineeringIncidentLearningReliability
Add more methods