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 |  Architecture C4 Model |  Product Discovery Opportunity Interview |  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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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 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 | Low | Medium | Medium |
Timedifferent | 30–60 min per interview | 1-4 h | 30-60 min je Interview | 1-2 h Setup, laufend |
Participantsdifferent | 1 participant per interview | 1-5 | 5-12 Interviews | 2-6 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | Context Diagram, Container Diagram, Component Diagram | Interview Notes, Opportunity Themes, Customer Quotes | Opportunity Solution Tree, Experiment Backlog, Learning Log |
Tagsno overlap | QualitativeResearchCustomerDiscovery | ArchitectureCommunicationVisualization | DiscoveryInterviewsOpportunityCustomer | DiscoveryOutcomesExperimentsOpportunity |