View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Hypothesis-Driven TroubleshootingExpectation MappingRoot Cause AnalysisSpotify Model Mapping
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Facilitation Expectation Mapping |  Operations Root Cause Analysis |  Team Design Spotify Model 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 roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-240 min | 45-90 min | 1-4 h | 90-180 min |
Participantsdifferent | 1-6 | 3-12 | 3-8 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Expectation Map, Alignment Notes, Agreements | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Spotify Model Map, Action List |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | AlignmentStakeholdersTeam | Root causeProblem solvingQualityIncident | TeamOrganizationAlignmentDiagnosis |