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 Hypothesis-Driven Troubleshooting |  Facilitation Alignment Mapping |  Team Design Spotify Model Mapping |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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. | 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-240 min | 1-2 h | 90-180 min | 60–90 min |
Participantsdifferent | 1-6 | 4-12 | 5-15 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Alignment Map, Open Issues, Decision Questions | Spotify Model Map, Action List | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | AlignmentStakeholdersStrategyFacilitation | TeamOrganizationAlignmentDiagnosis | StakeholdersAlignmentFacilitationChange |