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 shared options, independently placed voting dots, and a highlighted shortlist.
Facilitation
Dot Voting
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
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 a workshop has produced too many options and the group needs to condense quickly, dot voting makes preferences visible in a short time. It bundles individual votes into a solid signal for the next selection.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
LowLowMediumLow
Timedifferent
20-60 min5-15 minAs needed30-60 min
Participantsdifferent
1-43-204-151-5
Formatdifferent
AsyncWorkshopWorkshop + asyncAsync
Outputdifferent
Runbook, Checklist, Escalation PathRanked list, Consensus signal, ShortlistIncident Log, Action Tracker, Stakeholder UpdatesABC Classification, Focus Rules, Control List
Tagsno overlap
OperationsReliabilityDocumentation
FacilitationVotingConsensusPrioritization
IncidentOperationsReliability
PrioritizationOperationsPortfolio
Add more methods