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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Flywheel.
Growth
Flywheel
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.
Complexitydifferent
MediumLowMediumLow
Timedifferent
Multiple workshops over several weeks30 min Setup, dann laufend60-120 min20-40 min initial, dann laufend
Participantsdifferent
2-81-3 maintaining, briefing for everyone3-83-15
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkRAID Log, Status Report SourceFlywheel Map, Friction Points, Growth Levers, Experiment BacklogROAM Board, Owner List
Tagsno overlap
GrowthBehaviorRetention
RiskTrackingStakeholdersGovernance
GrowthRetentionConversion
RiskAgileTrackingAlignment
Add more methods