View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research User Interviews |  Product Discovery Opportunity Interview |  Architecture arc42 |  Product Discovery Opportunity Solution Tree |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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. | 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 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 | 30–60 min per interview | 30-60 min je Interview | 1-2 Tage | 1-2 h Setup, laufend |
Participantsdifferent | 1 participant per interview | 5-12 Interviews | 1-4 | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Interview Notes, Opportunity Themes, Customer Quotes | Architecture Document, Context View, Runtime View, Deployment View | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | QualitativeResearchCustomerDiscovery | DiscoveryInterviewsOpportunityCustomer | ArchitectureDocumentationCommunication | DiscoveryOutcomesExperimentsOpportunity |