View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Opportunity Solution Tree |  Architecture Architecture Decision Record |  Knowledge Modeling Event Modeling |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic. | 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 | Medium | Medium |
Timedifferent | 1-2 h Setup, laufend | 15-45 min | 2-6 h | 1-5 Tage |
Participantsdifferent | 2-6 | 1-3 | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Opportunity Solution Tree, Experiment Backlog, Learning Log | ADR File, Decision Log, Rationale | Event Model, UI Flow, Commands, Read Models | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | DiscoveryOutcomesExperimentsOpportunity | ArchitectureRationaleDocumentationGovernance | EventsBlueprintDomain-Driven DesignBehavior | ValidationExperimentsDemandDiscovery |