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 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
Paper illustration for Learning Review.
Operations
Learning Review
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Purposedifferent
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 a project phase with mixed results, the method makes learning from the individual case reusable. It connects events, decisions, and systemic conditions into robust insights.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
30-60 minAs needed1-3 h30-90 min
Participantsdifferent
2-84-153-103-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
ICE Table, Top Idea ListIncident Log, Action Tracker, Stakeholder UpdatesLearning Review Notes, System Factors, Improvement ActionsPostmortem Doc, Action Items, Timeline
Tagsno overlap
PrioritizationScoringGrowthDecision
IncidentOperationsReliability
LearningRetrospectiveIncidentOperations
Site Reliability EngineeringIncidentLearningReliability
Add more methods