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 Incident Timeline Analysis.
DevOps
Incident Timeline Analysis
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.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
MediumLowMedium
Timedifferent
60-180 min30-60 min1-2 h
Participantsdifferent
3-102-84-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Incident Timeline, Evidence Log, Delay Analysis, Improvement ActionsPower Interest Grid, Strategy per StakeholderAlignment Map, Open Issues, Decision Questions
Tagsno overlap
IncidentTimelineSite Reliability Engineering
StakeholdersFacilitationAlignmentPlanning
AlignmentStakeholdersStrategyFacilitation
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