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 Expectation Mapping |  Operations 5 Whys |  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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | Low | Medium |
Timedifferent | 30-240 min | 45-90 min | 15-30 min | 90-180 min |
Participantsdifferent | 1-6 | 3-12 | 2-6 | 5-15 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Expectation Map, Alignment Notes, Agreements | Root cause notes, Countermeasures | Spotify Model Map, Action List |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | AlignmentStakeholdersTeam | Root causeIncidentLeanProblem solving | TeamOrganizationAlignmentDiagnosis |