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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for ABC Analysis
Operations
ABC Analysis
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.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.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.With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention.
Complexitydifferent
LowMediumMediumLow
Timedifferent
30-60 min30-90 minAs needed30-60 min
Participantsdifferent
2-83-124-151-5
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
ICE Table, Top Idea ListPostmortem Doc, Action Items, TimelineIncident Log, Action Tracker, Stakeholder UpdatesABC Classification, Focus Rules, Control List
Tagsno overlap
PrioritizationScoringGrowthDecision
Site Reliability EngineeringIncidentLearningReliability
IncidentOperationsReliability
PrioritizationOperationsPortfolio
Add more methods