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 | ![]() UX Research Usability Testing | ![]() Architecture Architecture Communication Canvas | ![]() Architecture arc42 |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | Medium | Medium | Low |
Timedifferent | 20-45 min | 1-2 h je Session | 60-120 min | 1-2 Tage |
Participantsdifferent | Based on research question | Based on research question | 2-8 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Content groups, Label set, IA hypotheses | Usability Issues, Severity List, Recommendations | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | Information architectureNavigationStructure | ValidationUXPrototype | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |



