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 RecordDesign ThinkingFailure Mode and Effects AnalysisFishbone Diagram
| Criterion |  Architecture Architecture Decision Record |  Innovation Design Thinking |  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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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 | High | High | Low |
Timedifferent | 15-45 min | 1 Tag bis mehrere Wochen | 2-6 h | 30-60 min |
Participantsdifferent | 1-3 | 4-10 | 3-10 | 2-8 |
Formatdifferent | Async | Workshop | Workshop | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Problem Statement, Prototype, Test Learnings | FMEA Table, Risk Priority, Mitigation Actions | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | InnovationPrototypeResearch | RiskQualityOperationsRoot cause | Root causeQualityOperations |