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
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
Paper illustration of a Test Card with four fields for hypothesis, test, metric, and success threshold.
Product Discovery
Test Card
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.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.The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success.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
LowLowLowHigh
Timedifferent
1-2 h1-5 Tage20-35 min1-4 Wochen
Participantsdifferent
2-8Nutzertraffic1-51-6
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeInterest Metrics, Conversion Signal, Learning NoteTest Card with a pre-set thresholdExperiment results, Decision log, Learning summary
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ValidationExperimentsDemandGrowth
ExperimentsValidationDiscoveryHypothesis
ExperimentsGrowthAnalyticsValidation
Add more methods