methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Diary Study.
UX Research
Diary Study
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
A/B Testing workspace showing the question, observations, and next decision.
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
MediumMediumLowHigh
Timedifferent
1-4 Wochen2-6 h1-5 Tage1-4 Wochen
Participantsdifferent
5-202-8Nutzertraffic1-6
Formatdifferent
AsyncWorkshop + asyncAsyncAsync
Outputdifferent
Diary Entries, Longitudinal Patterns, Experience TimelineEvent Model, UI Flow, Commands, Read ModelsInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
UX researchTrackingBehavior
EventsBlueprintDomain-Driven DesignBehavior
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods