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 Architecture Decision Record |  Decision Making Assumption Surfacing |  Architecture Request for Comments |
|---|---|---|---|---|
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 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. | 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. |
Complexitydifferent | Low | Low | Low | Medium |
Timedifferent | 60-90 min | 15-45 min | 45-90 min | 1-3 Wochen vom Draft bis zur Entscheidung |
Participantsdifferent | 4-12 | 1-3 | 2-8 | 3-20 Reviewer |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | ADR File, Decision Log, Rationale | Assumption List, Critical Assumptions, Learning Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets |
Tagsno overlap | RiskArchitectureWorkshopValidation | ArchitectureRationaleDocumentationGovernance | AssumptionsRiskDecisionDiscovery | ArchitectureDecisionAsyncGovernance |