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 | ![]() Knowledge Modeling Event Modeling | ![]() 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. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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 | 2-6 h | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 5-20 | 2-8 | Nutzertraffic | 1-6 |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | Diary Entries, Longitudinal Patterns, Experience Timeline | Event Model, UI Flow, Commands, Read Models | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | UX researchTrackingBehavior | EventsBlueprintDomain-Driven DesignBehavior | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |



