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 |  Operations 5 Whys |  Team Design Spotify Model Mapping |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | 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. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-240 min | 15-30 min | 90-180 min | 45-90 min |
Participantsdifferent | 1-6 | 2-6 | 5-15 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Root cause notes, Countermeasures | Spotify Model Map, Action List | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | Root causeIncidentLeanProblem solving | TeamOrganizationAlignmentDiagnosis | LeanProblem solvingCoachingOperations |