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 Solution Interview |  Architecture Architecture Decision Record |  Product Discovery Assumption Mapping |  Product Discovery Riskiest Assumption Test |
|---|---|---|---|---|
Purposedifferent | When a solution idea is already on the table, it checks how it is understood and evaluated. It looks for resonance, objections, and missing fit early in the conversation. | 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. | 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 | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min je Interview | 15-45 min | 45-60 min | 1-2 Wochen pro Iteration |
Participantsdifferent | 5-10 Interviews | 1-3 | 2-8 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | ADR File, Decision Log, Rationale | Assumption map, Test backlog, Risk ranking | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | ValidationInterviewsPrototype | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskExperimentsValidation | ExperimentsValidationDiscoveryAssumptions |