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 of Hooked Model with its method-specific working model.
Growth
Hooked Model
Paper illustration for Flywheel.
Growth
Flywheel
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.The Hooked Model helps clarify engagement loops, user behavior, and experiments. It makes repeat behavior measurable and captures the result as a hooked loop, trigger map, and reward design.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.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
1-2 hMultiple workshops over several weeks60-120 min1-4 Wochen
Participantsdifferent
2-82-83-81-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopAsync
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeHooked loop, Trigger map, Reward design, Ethics checkFlywheel Map, Friction Points, Growth Levers, Experiment BacklogExperiment results, Decision log, Learning summary
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
GrowthBehaviorRetention
GrowthRetentionConversion
ExperimentsGrowthAnalyticsValidation
Add more methods