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
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
MediumLowHighLow
Timedifferent
Multiple workshops over several weeks1-2 h1-4 Wochen1-2 h
Participantsdifferent
2-83-101-63-8
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkArchitecture Canvas, Goals, Constraints, Quality AttributesExperiment results, Decision log, Learning summaryInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
GrowthBehaviorRetention
CanvasArchitectureAlignmentWorkshop
ExperimentsGrowthAnalyticsValidation
AlignmentArchitectureCanvas
Add more methods