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 RecordHEART FrameworkFailure Mode and Effects AnalysisFishbone Diagram
| Criterion |  Architecture Architecture Decision Record |  UX Research HEART Framework |  Operations Failure Mode and Effects Analysis |  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. | Helps clarify observations, needs, and patterns in concrete terms. It groups observations into patterns, questions, and decisions. The result is captured as a HEART-GSM table and dashboard. | 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. | 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 | Medium | High | Low |
Timedifferent | 15-45 min | 120 min initial, dann laufend | 2-6 h | 30-60 min |
Participantsdifferent | 1-3 | 3-6 | 3-10 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | HEART-GSM Table, Dashboard | FMEA Table, Risk Priority, Mitigation Actions | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | MetricsUX researchMeasurementSatisfaction | RiskQualityOperationsRoot cause | Root causeQualityOperations |