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 Flywheel.
Growth
Flywheel
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration for Smoke Test.
Product Discovery
Smoke Test
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.Growth often breaks down where a reinforcing mechanism builds up too much friction. A Flywheel shows the cycle of value, repetition, and reinforcement meant to sustain growth.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.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.
Complexitydifferent
LowMediumHighLow
Timedifferent
1-2 h60-120 min1-4 Wochen1-5 Tage
Participantsdifferent
2-83-81-6Nutzertraffic
Formatdifferent
WorkshopWorkshopAsyncAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summaryInterest Metrics, Conversion Signal, Learning Note
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
ValidationExperimentsDemandGrowth
Add more methods