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 Alignment Mapping |  Architecture Views and Beyond |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
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 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-90 min | 1-2 h | 1-3 Tage | 60-90 min |
Participantsdifferent | 3-12 | 4-12 | 1-4 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Alignment Map, Open Issues, Decision Questions | Architecture Views, Cross-view Notes, Rationale | Salience Diagram, Strategy per Class |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | AlignmentStakeholdersStrategyFacilitation | DocumentationStakeholdersArchitecture | StakeholdersFacilitationAlignmentGovernance |