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 MVP Test Matrix |  Product Discovery Problem Interview |  Product Discovery Riskiest Assumption Test |
|---|---|---|---|---|
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 several minimal variants compete to answer the same question, it makes comparing and choosing between them cleaner. It separates problem, assumption, solution, and evidence. The result is captured as a Test Matrix and a Test Plan. | 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 an idea hinges on one critical unknown, it prioritizes testing that exact piece of uncertainty first. It separates problem, assumption, solution, and evidence. The result is captured as a prioritized list of assumptions, a test plan, and a result report. |
Complexitydifferent | Low | Medium | Medium | Medium |
Timedifferent | 15-45 min | 45-75 min | 30-60 min je Interview | 1-2 Wochen pro Iteration |
Participantsdifferent | 1-3 | 2-8 | 5-12 Interviews | 2-6 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Test Matrix, Test Plan | Problem Evidence, Risk Notes, Customer Segments | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ExperimentsValidationDiscoveryOptions | DiscoveryInterviewsValidation | ExperimentsValidationDiscoveryAssumptions |