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 RecordFishbone DiagramScatter DiagramFailure Mode and Effects Analysis
| Criterion |  Architecture Architecture Decision Record |  Operations Fishbone Diagram |  Operations Scatter Diagram |  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. | 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. | When the question is whether two measures are related, the method makes patterns in the data picture visible. It separates felt correlations from relationships that actually show up in the data. | 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 | Low | Low | High |
Timedifferent | 15-45 min | 30-60 min | 30-90 min | 2-6 h |
Participantsdifferent | 1-3 | 2-8 | 1-4 | 3-10 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Fishbone Diagram, Cause Categories, Investigation Backlog | Scatter Plot, Korrelationsnotiz, Hypothesenliste | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Root causeQualityOperations | Root causeQualityVisualization | RiskQualityOperationsRoot cause |