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 the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
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 group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
20-60 min1-3 hAs needed1-2 h
Participantsdifferent
1-45-304-154-12
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Runbook, Checklist, Escalation PathConsensus Clusters, Theme Titles, Priority AreasIncident Log, Action Tracker, Stakeholder UpdatesAlignment Map, Open Issues, Decision Questions
Tagsno overlap
OperationsReliabilityDocumentation
FacilitationConsensusWorkshopAlignment
IncidentOperationsReliability
AlignmentStakeholdersStrategyFacilitation
Add more methods