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 a decision table with criteria rows, weighted ratings, and a narrowly leading alternative.
Decision Making
Decision Matrix
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a scoring table with four factor columns, a calculator and three ordered initiative cards.
Product Strategy
RICE Scoring
Purposedifferent
When several options collide with several criteria, comparison quickly becomes subjective. A Decision Matrix makes the trade-off visible and brings weighting, criteria, and options into a shared logic.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.When many initiatives compete for the same resources, it brings reach, impact, confidence, and effort into one shared ranking. It makes prioritization economically connectable.
Complexitysame
MediumMediumMedium
Timedifferent
45-90 minAs needed60-90 min
Participantsdifferent
2-84-152-10
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Decision Matrix, Scoring Rationale, Selected OptionIncident Log, Action Tracker, Stakeholder UpdatesRICE Scores, Ranked List, Assumption Log
Tagsno overlap
DecisionCriteriaScoringTradeoffs
IncidentOperationsReliability
PrioritizationScoringRoadmapTradeoffs
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of ICE Scoring with its method-specific working model.
Product Strategy
ICE Scoring
Paper illustration for Trade-off Analysis.
Decision Making
Trade-off Analysis
Paper illustration for ABC Analysis
Operations
ABC Analysis
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem