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
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Paper illustration for Flywheel.
Growth
Flywheel
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.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.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.
Complexitydifferent
MediumLowLowMedium
Timedifferent
Multiple workshops over several weeks1-2 h1-2 h60-120 min
Participantsdifferent
2-83-103-83-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkArchitecture Canvas, Goals, Constraints, Quality AttributesInception Canvas, Risks, Goal List, Open QuestionsFlywheel Map, Friction Points, Growth Levers, Experiment Backlog
Tagsno overlap
GrowthBehaviorRetention
CanvasArchitectureAlignmentWorkshop
AlignmentArchitectureCanvas
GrowthRetentionConversion
Add more methods