View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Spotify Model Mapping |  DevOps Blameless Postmortem |  Facilitation Power Interest Grid |  Facilitation Stakeholder Salience Model |
|---|---|---|---|---|
Purposedifferent | When a team landscape has grown without clear grouping, it maps roles and relationships onto the Spotify model. It clarifies responsibility, interaction, and load between teams. The result is captured as a Spotify model map and action list. | 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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 90-180 min | 30-90 min | 30-60 min | 60-90 min |
Participantsdifferent | 5-15 | 3-12 | 2-8 | 3-6 |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Spotify Model Map, Action List | Postmortem Doc, Action Items, Timeline | Power Interest Grid, Strategy per Stakeholder | Salience Diagram, Strategy per Class |
Tagsno overlap | TeamOrganizationAlignmentDiagnosis | Site Reliability EngineeringIncidentLearningReliability | StakeholdersFacilitationAlignmentPlanning | StakeholdersFacilitationAlignmentGovernance |