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 Problem Interview |  Architecture arc42 |  UX Research User Interviews |  Product Discovery Opportunity Interview |
|---|---|---|---|---|
Purposedifferent | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-60 min je Interview | 1-2 Tage | 30–60 min per interview | 30-60 min je Interview |
Participantsdifferent | 5-12 Interviews | 1-4 | 1 participant per interview | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Architecture Document, Context View, Runtime View, Deployment View | Interview Notes, Themes, Insight Summary | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | DiscoveryInterviewsValidation | ArchitectureDocumentationCommunication | QualitativeResearchCustomerDiscovery | DiscoveryInterviewsOpportunityCustomer |