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 Fake Door Test |  Product Discovery Problem Interview |
|---|---|---|---|---|
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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. | 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min je Interview | 15-45 min | 1-5 Tage | 30-60 min je Interview |
Participantsdifferent | 5-10 Interviews | 1-3 | Nutzertraffic | 5-12 Interviews |
Formatdifferent | Workshop + async | Async | Async | Workshop + async |
Outputdifferent | Solution Feedback, Objection List, Validation Notes | ADR File, Decision Log, Rationale | Click Data, Interest Signal, Learning Decision | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | ValidationInterviewsPrototype | ArchitectureRationaleDocumentationGovernance | ValidationExperimentsDemandDiscovery | DiscoveryInterviewsValidation |