View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations Runbook |  Growth Hooked Model |  Product Discovery Fake Door Test |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | For recurring operational tasks or incidents, the method keeps solid action logic ready. It reduces uncertainty when time pressure, role changes, or rare situations demand fast access. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | 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 | Low | Medium | Medium | High |
Timedifferent | 20-60 min | Multiple workshops over several weeks | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 1-4 | 2-8 | Nutzertraffic | 1-6 |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | Runbook, Checklist, Escalation Path | Hooked loop, Trigger map, Reward design, Ethics check | Click Data, Interest Signal, Learning Decision | Experiment results, Decision log, Learning summary |
Tagsno overlap | OperationsReliabilityDocumentation | GrowthBehaviorRetention | ValidationExperimentsDemandDiscovery | ExperimentsGrowthAnalyticsValidation |