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
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Incident Command workspace showing the question, observations, and next decision.
DevOps
Incident Command
Paper illustration for 3-Circle Venn Diagram
Facilitation
3-Circle Venn Diagram
Purposedifferent
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.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 three perspectives matter at the same time, a Three-Circle Venn Diagram shows the overlaps and remainders precisely. It makes visible where shared effect arises and where only a partial perspective applies.
Complexitydifferent
LowMediumLow
Timedifferent
60–90 minAs needed15-45 min
Participantsdifferent
2-84-152-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Stakeholder Map, Engagement Plan, Risk NotesIncident Log, Action Tracker, Stakeholder UpdatesVenn Diagram, Overlap Notes, Differentiators
Tagsno overlap
StakeholdersAlignmentFacilitationChange
IncidentOperationsReliability
ComparisonFacilitationAlignment
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem