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
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem
Paper illustration for ABC Analysis
Operations
ABC Analysis
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.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.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
LowLowMediumLow
Timedifferent
20-60 min30-60 min30-90 min30-60 min
Participantsdifferent
1-42-83-121-5
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathICE Table, Top Idea ListPostmortem Doc, Action Items, TimelineABC Classification, Focus Rules, Control List
Tagsno overlap
OperationsReliabilityDocumentation
PrioritizationScoringGrowthDecision
Site Reliability EngineeringIncidentLearningReliability
PrioritizationOperationsPortfolio
Add more methods