View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:User InterviewsArchitecture Decision RecordFishbone DiagramFailure Mode and Effects Analysis
| Criterion |  UX Research User Interviews |  Architecture Architecture Decision Record |  Operations Fishbone Diagram |  Operations Failure Mode and Effects Analysis |
|---|---|---|---|---|
Purposedifferent | When teams derive needs only from assumptions and real motives are missing, user interviews give direct access to behavior and meaning. Conversations from the target group's everyday life make patterns, tensions, and open questions solidly visible. | 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 | Low | Low | Low | High |
Timedifferent | 30–60 min per interview | 15-45 min | 30-60 min | 2-6 h |
Participantsdifferent | 1 participant per interview | 1-3 | 2-8 | 3-10 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Interview Notes, Themes, Insight Summary | ADR File, Decision Log, Rationale | Fishbone Diagram, Cause Categories, Investigation Backlog | FMEA Table, Risk Priority, Mitigation Actions |
Tagsno overlap | QualitativeResearchCustomerDiscovery | ArchitectureRationaleDocumentationGovernance | Root causeQualityOperations | RiskQualityOperationsRoot cause |