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 Polarity Map with two poles and four quadrants
Systems Thinking
Polarity Mapping
Runbook workspace showing the question, observations, and next decision.
Operations
Runbook
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
Purposedifferent
Polarity Mapping makes tensions between two opposing poles tangible, such as standardization and adaptation or control and autonomy. The method guards against making apparent either-or decisions prematurely.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 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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-2 h20-60 min45-90 minAs needed
Participantsdifferent
3-121-42-84-15
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Polarity Map, Warning Signs, Balance ActionsRunbook, Checklist, Escalation PathDecision Matrix, Scoring Rationale, Selected OptionIncident Log, Action Tracker, Stakeholder Updates
Tagsno overlap
Systems thinkingTradeoffsLeadership
OperationsReliabilityDocumentation
DecisionCriteriaScoringTradeoffs
IncidentOperationsReliability
Add more methods