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 |  Decision Making Assumption Surfacing |  Architecture Request for Comments |  Product Discovery Riskiest Assumption Test |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | 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 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 | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Wochen pro Iteration |
Participantsdifferent | 5-12 Interviews | 2-8 | 3-20 Reviewer | 2-6 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Assumption List, Critical Assumptions, Learning Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Prioritized Assumption List, Test Plan, Results Report |
Tagsno overlap | DiscoveryInterviewsValidation | AssumptionsRiskDecisionDiscovery | ArchitectureDecisionAsyncGovernance | ExperimentsValidationDiscoveryAssumptions |