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 Team Charter |  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 a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. | 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 |
Timedifferent | 30-90 min | 2-4 h | 60-90 min |
Participantsdifferent | 3-12 | 3-12 | 3-6 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Postmortem Doc, Action Items, Timeline | Team Charter, Working Norms, Role Notes | Salience Diagram, Strategy per Class |
Tagsno overlap | Site Reliability EngineeringIncidentLearningReliability | TeamAlignmentCollaboration | StakeholdersFacilitationAlignmentGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
