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
Paper illustration for Flywheel.
Growth
Flywheel
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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.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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
Multiple workshops over several weeks1-2 h60-120 min1-3 h
Participantsdifferent
2-83-103-85-30
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkArchitecture Canvas, Goals, Constraints, Quality AttributesFlywheel Map, Friction Points, Growth Levers, Experiment BacklogConsensus Clusters, Theme Titles, Priority Areas
Tagsno overlap
GrowthBehaviorRetention
CanvasArchitectureAlignmentWorkshop
GrowthRetentionConversion
FacilitationConsensusWorkshopAlignment
Add more methods