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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Flywheel.
Growth
Flywheel
Paper illustration for DACI
Decision Making
DACI
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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
Multiple workshops over several weeks1-3 Wochen vom Draft bis zur Entscheidung60-120 min30-60 min
Participantsdifferent
2-83-20 Reviewer3-82-10
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsFlywheel Map, Friction Points, Growth Levers, Experiment BacklogDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
GrowthBehaviorRetention
ArchitectureDecisionAsyncGovernance
GrowthRetentionConversion
DecisionRolesGovernanceAlignment
Add more methods