View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Fault Isolation |  Facilitation Stakeholder Salience Model |  Team Design Spotify Model Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | In technical failures, the visible symptom often gets mixed up with the actual cause. Fault Isolation narrows the fault space and progressively reduces which part of the system is truly affected. | 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. | 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. | 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 | Medium | Low |
Timedifferent | 30-180 min | 60-90 min | 90-180 min | 60–90 min |
Participantsdifferent | 1-6 | 3-6 | 5-15 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Fault Isolation Map, Test Log, Excluded Hypotheses, Narrowed Fault Area | Salience Diagram, Strategy per Class | Spotify Model Map, Action List | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | TroubleshootingDiagnosisEngineering | StakeholdersFacilitationAlignmentGovernance | TeamOrganizationAlignmentDiagnosis | StakeholdersAlignmentFacilitationChange |