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 Request for Comments |  Decision Making Risk Matrix |  Architecture Risk Storming |
|---|---|---|---|
Purposedifferent | 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. | When a project faces many possible disruptions, it quickly becomes unclear which risks deserve attention first. It separates options, evaluation criteria, and open risks. The result is captured as a Risk Matrix and a Top Risk List. | 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. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 30-60 min | 60-90 min |
Participantsdifferent | 3-20 Reviewer | 3-10 | 4-12 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Risk Matrix, Top Risk List | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | RiskDecisionPrioritizationAssessment | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
