View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Architecture Decision Record |  Product Discovery Opportunity Interview |  Product Discovery Problem Interview |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
Purposedifferent | 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 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 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. | When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 30-60 min je Interview | 30-60 min je Interview | 30-60 min |
Participantsdifferent | 1-3 | 5-12 Interviews | 5-12 Interviews | 1-5 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Interview Notes, Opportunity Themes, Customer Quotes | Problem Evidence, Risk Notes, Customer Segments | Completed Experiment Canvas, Success Metric |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | DiscoveryInterviewsOpportunityCustomer | DiscoveryInterviewsValidation | ExperimentsValidationDiscoveryHypothesis |