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 |  Delivery RAID Log |  Facilitation Stakeholder 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. |
Complexitydifferent | Medium | Medium | Low | Low |
Timedifferent | 30-90 min | 60-90 min | 30 min Setup, dann laufend | 60–90 min |
Participantsdifferent | 3-12 | 3-6 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Salience Diagram, Strategy per Class | RAID Log, Status Report Source | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | StakeholdersFacilitationAlignmentGovernance | RiskTrackingStakeholdersGovernance | StakeholdersAlignmentFacilitationChange |