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
Paper illustration of a four-column Kanban board with limited ongoing work, a visible blocker and a review loop.
Engineering
Kanban
Value Stream Mapping workspace showing the question, observations, and next decision.
Delivery
Value Stream Mapping
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.When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable.When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
Multiple workshops over several weeksOngoing1-3 h60-120 min
Participantsdifferent
2-82-124-103-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkKanban board, WIP policies, Flow metricsCurrent-state map, Future-state map, Bottleneck listFlywheel Map, Friction Points, Growth Levers, Experiment Backlog
Tagsno overlap
GrowthBehaviorRetention
FlowVisual managementDelivery
LeanFlowWasteDelivery
GrowthRetentionConversion
Add more methods