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 the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement.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
MediumMediumLowMedium
Timedifferent
1-3 hAs needed20-45 min1-2 h
Participantsdifferent
5-304-153-124-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Consensus Clusters, Theme Titles, Priority AreasIncident Log, Action Tracker, Stakeholder UpdatesLessons learned, Action items, Event summaryAlignment Map, Open Issues, Decision Questions
Tagsno overlap
FacilitationConsensusWorkshopAlignment
IncidentOperationsReliability
LearningOperationsImprovement
AlignmentStakeholdersStrategyFacilitation
Add more methods