View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture Risk Storming |  Decision Making Assumption Surfacing |  Product Discovery Problem Interview |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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. | 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 60-90 min | 45-90 min | 30-60 min je Interview | 45-60 min |
Participantsdifferent | 4-12 | 2-8 | 5-12 Interviews | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Assumption List, Critical Assumptions, Learning Plan | Problem Evidence, Risk Notes, Customer Segments | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskArchitectureWorkshopValidation | AssumptionsRiskDecisionDiscovery | DiscoveryInterviewsValidation | AssumptionsRiskExperimentsValidation |