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 |  Operations Change Analysis |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|
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. | For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise. | For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability. |
Complexitydifferent | Medium | Medium | High |
Timedifferent | 1-3 Wochen vom Draft bis zur Entscheidung | 45-120 min | 2-6 h |
Participantsdifferent | 3-20 Reviewer | 2-6 | 3-10 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Change Matrix, Cause Hypotheses, Validation Questions, Action List | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | ArchitectureDecisionAsyncGovernance | ChangeRoot causeTroubleshootingComparison | RiskQualityOperationsRoot cause |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
