View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Customer Journey MappingArchitecture Decision RecordFishbone DiagramFailure Mode and Effects Analysis
| Criterion |  UX Research Customer Journey Mapping |  Architecture Architecture Decision Record |  Operations Fishbone Diagram |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | 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. | 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 | Medium | Low | Low | High |
Timedifferent | 2-4 h | 15-45 min | 30-60 min | 2-6 h |
Participantsdifferent | 4-10 | 1-3 | 2-8 | 3-10 |
Formatdifferent | Workshop | Async | Workshop | Workshop |
Outputdifferent | Journey Map, Pain-point List, Opportunity Backlog | ADR File, Decision Log, Rationale | Fishbone Diagram, Cause Categories, Investigation Backlog | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | JourneyServiceService design | ArchitectureRationaleDocumentationGovernance | Root causeQualityOperations | RiskQualityOperationsRoot cause |