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 ATAM (Architecture Tradeoff Analysis Method) | ![]() Operations 5 Whys | ![]() Operations Root Cause Analysis |
|---|---|---|---|---|
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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. |
Complexitydifferent | Low | High | Low | Medium |
Timedifferent | 20-45 min | Several meetings plus preparation and analysis; total effort depends on scope | 15-30 min | 1-4 h |
Participantsdifferent | Based on research question | Evaluation team, architects, and relevant stakeholders | 2-6 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Content groups, Label set, IA hypotheses | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Root cause notes, Countermeasures | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan |
Tagsno overlap | Information architectureNavigationStructure | ArchitectureQualityRiskTradeoffsStakeholders | Root causeIncidentLeanProblem solving | Root causeProblem solvingQualityIncident |



