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 Architecture Decision Record |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-60 min je Interview | 45-90 min | 15-45 min | 45-60 min |
Participantsdifferent | 5-12 Interviews | 2-8 | 1-3 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Assumption List, Critical Assumptions, Learning Plan | ADR File, Decision Log, Rationale | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | DiscoveryInterviewsValidation | AssumptionsRiskDecisionDiscovery | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskExperimentsValidation |