View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() DevOps Blameless Postmortem | ![]() Facilitation Stakeholder Salience Model | ![]() Decision Making Decision Rights Mapping | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | 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. | In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-90 min | 60-90 min | 90-180 min | 1-2 h |
Participantsdifferent | 3-12 | 3-6 | 4-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Salience Diagram, Strategy per Class | Decision Rights Matrix, Agreement | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | StakeholdersFacilitationAlignmentGovernance | DecisionGovernanceAlignmentResponsibility | AlignmentStakeholdersStrategyFacilitation |



