View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Product Discovery Opportunity Interview |  Product Discovery Fake Door Test |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
Purposedifferent | 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 opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | 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 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. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 1-2 Tage | 30-60 min je Interview | 1-5 Tage | 1-2 h Setup, laufend |
Participantsdifferent | 1-4 | 5-12 Interviews | Nutzertraffic | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Interview Notes, Opportunity Themes, Customer Quotes | Click Data, Interest Signal, Learning Decision | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | ArchitectureDocumentationCommunication | DiscoveryInterviewsOpportunityCustomer | ValidationExperimentsDemandDiscovery | DiscoveryOutcomesExperimentsOpportunity |