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
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration for Root Cause Analysis.
Operations
Root Cause Analysis
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 there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another.
Complexitydifferent
MediumLowLowMedium
Timedifferent
Multiple workshops over several weeks30-120 min15-30 min1-4 h
Participantsdifferent
2-82-62-63-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Hooked loop, Trigger map, Reward design, Ethics checkObservation Notes, Improvement IdeasRoot cause notes, CountermeasuresProblem Statement, Cause Hypotheses, Confirmed Causes, Action Plan
Tagsno overlap
GrowthBehaviorRetention
LeanObservationProcessOperations
Root causeIncidentLeanProblem solving
Root causeProblem solvingQualityIncident
Add more methods