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 for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration for Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Purposedifferent
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.For an incident with an unclear sequence, the method makes the timeline precisely visible. It separates perception, reaction, and delay so cause and effect become more clearly readable.When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.
Complexitydifferent
MediumMediumLow
Timedifferent
1-2 h60-180 min30-60 min
Participantsdifferent
4-123-102-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop
Outputdifferent
Alignment Map, Open Issues, Decision QuestionsIncident Timeline, Evidence Log, Delay Analysis, Improvement ActionsPower Interest Grid, Strategy per Stakeholder
Tagsno overlap
AlignmentStakeholdersStrategyFacilitation
IncidentTimelineSite Reliability Engineering
StakeholdersFacilitationAlignmentPlanning
Add more methods

Often compared together

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

Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model
Paper illustration for 3-Circle Venn Diagram
Facilitation
3-Circle Venn Diagram
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem