View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations 5 Whys |  Product Discovery Smoke Test |  Operations A3 Problem Solving |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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. | When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Low | Low | Medium | High |
Timedifferent | 15-30 min | 1-5 Tage | 45-90 min | 1-4 Wochen |
Participantsdifferent | 2-6 | Nutzertraffic | 2-5 | 1-6 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Root cause notes, Countermeasures | Interest Metrics, Conversion Signal, Learning Note | A3 Report, Action Plan, Root Cause Analysis | Experiment results, Decision log, Learning summary |
Tagsno overlap | Root causeIncidentLeanProblem solving | ValidationExperimentsDemandGrowth | LeanProblem solvingCoachingOperations | ExperimentsGrowthAnalyticsValidation |