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 the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.
Complexitydifferent
MediumLowMediumHigh
Timedifferent
Multiple workshops over several weeks45-90 min45-60 min1-4 Wochen
Participantsdifferent
2-83-122-81-6
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkForce Field Map, Change Levers, Risk NotesAssumption map, Test backlog, Risk rankingExperiment results, Decision log, Learning summary
Tagsno overlap
GrowthBehaviorRetention
ChangeDecisionStrategy
AssumptionsRiskExperimentsValidation
ExperimentsGrowthAnalyticsValidation
Add more methods