View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Growth Hooked Model | ![]() Architecture arc42 | ![]() Product Discovery Smoke Test | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | Multiple workshops over several weeks | 1-2 Tage | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 2-8 | 1-4 | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Hooked loop, Trigger map, Reward design, Ethics check | Architecture Document, Context View, Runtime View, Deployment View | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | GrowthBehaviorRetention | ArchitectureDocumentationCommunication | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |



