View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations ABC Analysis |  Architecture Request for Comments |  Architecture Risk Storming |
|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | 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 | Low | Medium | Low |
Timedifferent | 30-60 min | 1-3 Wochen vom Draft bis zur Entscheidung | 60-90 min |
Participantsdifferent | 1-5 | 3-20 Reviewer | 4-12 |
Formatdifferent | Async | Async | Workshop |
Outputdifferent | ABC Classification, Focus Rules, Control List | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Annotated Diagram, Prioritized Risk List, Action Backlog |
Tagsno overlap | PrioritizationOperationsPortfolio | ArchitectureDecisionAsyncGovernance | RiskArchitectureWorkshopValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
