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 Interview |  Architecture Views and Beyond |  Architecture Architecture Decision Record |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
Purposedifferent | 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. | Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question. | 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. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | 1-3 Tage | 15-45 min | 1-2 h Setup, laufend |
Participantsdifferent | 5-12 Interviews | 1-4 | 1-3 | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Architecture Views, Cross-view Notes, Rationale | ADR File, Decision Log, Rationale | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | DocumentationStakeholdersArchitecture | ArchitectureRationaleDocumentationGovernance | DiscoveryOutcomesExperimentsOpportunity |