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 Usability Testing |  Architecture Architecture Decision Record |  UX Research Card Sorting |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | When a product is built but people get stuck on tasks, usability testing shows the friction at concrete points. Observed use instead of self-report makes visible where orientation, understanding, or interaction breaks down. | 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. | 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. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-2 h je Session | 15-45 min | 20-45 min | 1-2 Tage |
Participantsdifferent | Based on research question | 1-3 | Based on research question | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Usability Issues, Severity List, Recommendations | ADR File, Decision Log, Rationale | Content groups, Label set, IA hypotheses | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ValidationUXPrototype | ArchitectureRationaleDocumentationGovernance | Information architectureNavigationStructure | ArchitectureDocumentationCommunication |