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 RecordCard SortingFailure Mode and Effects Analysis8D Problem Solving
| Criterion |  Architecture Architecture Decision Record |  UX Research Card Sorting |  Operations Failure Mode and Effects Analysis |  Operations 8D Problem Solving |
|---|---|---|---|---|
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. | When content only makes sense internally and users can't find the structure again, card sorting exposes their mental order. Terms, groups, and naming are then aligned with the target group's expectations. | 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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. |
Complexitydifferent | Low | Low | High | High |
Timedifferent | 15-45 min | 20-45 min | 2-6 h | 1-6 Wochen |
Participantsdifferent | 1-3 | Based on research question | 3-10 | 4-10 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Content groups, Label set, IA hypotheses | FMEA Table, Risk Priority, Mitigation Actions | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Information architectureNavigationStructure | RiskQualityOperationsRoot cause | QualityProblem solvingRoot cause |