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 | ![]() Delivery RAID Log | ![]() Product Discovery Opportunity Solution Tree | ![]() Product Discovery Opportunity Interview |
|---|---|---|---|---|
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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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. | 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 | Low | Low | Medium | Medium |
Timedifferent | 30–60 min per interview | 30 min Setup, dann laufend | 1-2 h Setup, laufend | 30-60 min je Interview |
Participantsdifferent | 1 participant per interview | 1-3 maintaining, briefing for everyone | 2-6 | 5-12 Interviews |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Themes, Insight Summary | RAID Log, Status Report Source | Opportunity Solution Tree, Experiment Backlog, Learning Log | Interview Notes, Opportunity Themes, Customer Quotes |
Tagsno overlap | QualitativeResearchCustomerDiscovery | RiskTrackingStakeholdersGovernance | DiscoveryOutcomesExperimentsOpportunity | DiscoveryInterviewsOpportunityCustomer |



