View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Affinity DiagrammingArchitecture Decision RecordFailure Mode and Effects AnalysisFishbone Diagram
| Criterion |  UX Research Affinity Diagramming |  Architecture Architecture Decision Record |  Operations Failure Mode and Effects Analysis |  Operations Fishbone Diagram |
|---|---|---|---|---|
Purposedifferent | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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. | 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 | Low | High | Low |
Timedifferent | 45–90 min | 15-45 min | 2-6 h | 30-60 min |
Participantsdifferent | 3-10 | 1-3 | 3-10 | 2-8 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | ADR File, Decision Log, Rationale | FMEA Table, Risk Priority, Mitigation Actions | Fishbone Diagram, Cause Categories, Investigation Backlog |
Tagsno overlap | SynthesisQualitativeRoot cause | ArchitectureRationaleDocumentationGovernance | RiskQualityOperationsRoot cause | Root causeQualityOperations |