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 Problem Interview |  Architecture Request for Comments |  Product Discovery MVP Test Matrix |  Product Discovery Learning Card |
|---|---|---|---|---|
Purposedifferent | 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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 30-60 min je Interview | 1-3 Wochen vom Draft bis zur Entscheidung | 45-75 min | 25-40 min |
Participantsdifferent | 5-12 Interviews | 3-20 Reviewer | 2-8 | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Test Matrix, Test Plan | Learning Card with evidence and next action |
Tagsno overlap | DiscoveryInterviewsValidation | ArchitectureDecisionAsyncGovernance | ExperimentsValidationDiscoveryOptions | ExperimentsValidationDiscoveryLearning |