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 of Hooked Model with its method-specific working model.
Growth
Hooked Model
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
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
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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
MediumLowLowHigh
Timedifferent
Multiple workshops over several weeks1-2 Tage1-5 Tage1-4 Wochen
Participantsdifferent
2-81-4Nutzertraffic1-6
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncAsync
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkArchitecture Document, Context View, Runtime View, Deployment ViewInterest Metrics, Conversion Signal, Learning NoteExperiment results, Decision log, Learning summary
Tagsno overlap
GrowthBehaviorRetention
ArchitectureDocumentationCommunication
ValidationExperimentsDemandGrowth
ExperimentsGrowthAnalyticsValidation
Add more methods