View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  UX Research Card Sorting |  Architecture arc42 |  Operations 5 Whys |  Operations 8D Problem Solving |
|---|---|---|---|---|
Purposedifferent | 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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | 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 | Low | High |
Timedifferent | 20-45 min | 1-2 Tage | 15-30 min | 1-6 Wochen |
Participantsdifferent | Based on research question | 1-4 | 2-6 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Content groups, Label set, IA hypotheses | Architecture Document, Context View, Runtime View, Deployment View | Root cause notes, Countermeasures | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan |
Tagsno overlap | Information architectureNavigationStructure | ArchitectureDocumentationCommunication | Root causeIncidentLeanProblem solving | QualityProblem solvingRoot cause |