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
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
Purposedifferent
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 a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
As needed60-90 min60–90 min1-3 h
Participantsdifferent
4-154-102-85-30
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Incident Log, Action Tracker, Stakeholder UpdatesProblem Cluster, Prioritized Challenge, ExperimentStakeholder Map, Engagement Plan, Risk NotesConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
IncidentOperationsReliability
FacilitationDecisionProblem solvingWorkshop
StakeholdersAlignmentFacilitationChange
FacilitationConsensusWorkshopAlignment
Add more methods