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 |  Delivery RAID Log |  Operations Fishbone Diagram |
|---|---|---|---|---|
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. | 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. | When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers. |
Complexitydifferent | Low | High | Low | Low |
Timedifferent | 15-45 min | 2-6 h | 30 min Setup, dann laufend | 30-60 min |
Participantsdifferent | 1-3 | 3-10 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Async | Workshop | Async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions | RAID Log, Status Report Source | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause | RiskTrackingStakeholdersGovernance | Root causeQualityOperations |