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 Architecture Decision Record | ![]() Operations Failure Mode and Effects Analysis | ![]() Operations Fault Tree Analysis |
|---|---|---|---|
Purposedifferent | 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. | 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. | For a critical top event with several possible triggers, the method logically models failure paths. It makes visible which combinations of conditions can lead to damage. |
Complexitydifferent | Low | High | High |
Timedifferent | 15-45 min | 2-6 h | 2-6 h |
Participantsdifferent | 1-3 | 3-10 | 3-8 |
Formatdifferent | Async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions | Fault Tree, Critical Paths, Cause Hypotheses, Control Actions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause | RiskRoot causeSafety |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






