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 |  Product Discovery Problem Interview |  Architecture Architecture Decision Record |  Decision Making Assumption Surfacing |
|---|---|---|---|---|
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. | 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 ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 60-90 min | 30-60 min je Interview | 15-45 min | 45-90 min |
Participantsdifferent | 4-12 | 5-12 Interviews | 1-3 | 2-8 |
Formatdifferent | Workshop | Workshop + async | Async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Problem Evidence, Risk Notes, Customer Segments | ADR File, Decision Log, Rationale | Assumption List, Critical Assumptions, Learning Plan |
Tagsno overlap | RiskArchitectureWorkshopValidation | DiscoveryInterviewsValidation | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskDecisionDiscovery |