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 |  Architecture Request for Comments |  Decision Making Assumption Surfacing |  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. | 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. | 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 60-90 min | 1-3 Wochen vom Draft bis zur Entscheidung | 45-90 min | 45-60 min |
Participantsdifferent | 4-12 | 3-20 Reviewer | 2-8 | 2-8 |
Formatdifferent | Workshop | Async | Workshop + async | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Assumption List, Critical Assumptions, Learning Plan | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | RiskArchitectureWorkshopValidation | ArchitectureDecisionAsyncGovernance | AssumptionsRiskDecisionDiscovery | AssumptionsRiskExperimentsValidation |