View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordOpportunity InterviewAffinity DiagrammingOpportunity Solution Tree
| Criterion |  Architecture Architecture Decision Record |  Product Discovery Opportunity Interview |  UX Research Affinity Diagramming |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
Purposedifferent | 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 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 research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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 | Low | Medium |
Timedifferent | 15-45 min | 30-60 min je Interview | 45–90 min | 1-2 h Setup, laufend |
Participantsdifferent | 1-3 | 5-12 Interviews | 3-10 | 2-6 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Interview Notes, Opportunity Themes, Customer Quotes | Theme clusters, Insight statements, Opportunity areas | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | DiscoveryInterviewsOpportunityCustomer | SynthesisQualitativeRoot cause | DiscoveryOutcomesExperimentsOpportunity |