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 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
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 stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy.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
MediumMediumLow
Timedifferent
60-180 min60-90 min15-45 min
Participantsdifferent
3-103-62-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + async
Outputdifferent
Incident Timeline, Evidence Log, Delay Analysis, Improvement ActionsSalience Diagram, Strategy per ClassVenn Diagram, Overlap Notes, Differentiators
Tagsno overlap
IncidentTimelineSite Reliability Engineering
StakeholdersFacilitationAlignmentGovernance
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
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Blameless Postmortem workspace showing the question, observations, and next decision.
DevOps
Blameless Postmortem