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 Opportunity Interview | ![]() Architecture Architecture Decision Record | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|
Purposedifferent | 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. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | 15-45 min | 45-60 min |
Participantsdifferent | 5-12 Interviews | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | ADR File, Decision Log, Rationale | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






