View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() UX Research Diary Study | ![]() Engineering Failure Scenario Analysis | ![]() Product Discovery Smoke Test | ![]() Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | When experiences build up over days or weeks and a single session cannot capture them, Diary Study records the course of everyday life. Recurring triggers, moods, and habits become visible this way, beyond the sharpness of memory. | In critical processes, it is not enough to plan only for the normal case. Failure Scenario Analysis looks at the path into failure and shows which failures, chains, and control gaps cause the most damage. | 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. | 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 | Medium | Medium | Low | High |
Timedifferent | 1-4 Wochen | 1-3 h | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 5-20 | 3-8 | Nutzertraffic | 1-6 |
Formatdifferent | Async | Workshop | Async | Async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Failure Scenarios, Risk Notes, Control Gaps, Test and Response Actions | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | UX researchTrackingBehavior | FailureResilienceRisk | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |



