View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordRoot Cause Tree AnalysisRAID LogFailure Mode and Effects Analysis
| Criterion |  Architecture Architecture Decision Record |  Operations Root Cause Tree Analysis |  Delivery RAID Log |  Operations Failure Mode and Effects 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 problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Low | Medium | Low | High |
Timedifferent | 15-45 min | 1-3 h | 30 min Setup, dann laufend | 2-6 h |
Participantsdifferent | 1-3 | 2-8 | 1-3 maintaining, briefing for everyone | 3-10 |
Formatdifferent | Async | Workshop | Async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Cause Tree, Evidence Notes, Countermeasures | RAID Log, Status Report Source | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Root causeTreeIncidentQuality | RiskTrackingStakeholdersGovernance | RiskQualityOperationsRoot cause |