View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Architecture Decision Record | ![]() UX Research Tree Testing | ![]() Architecture C4 Model | ![]() UX Research Card Sorting |
|---|---|---|---|---|
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 a navigation exists but search paths still fail, tree testing checks findability without visual distraction. The method shows whether labels, levels, and paths really lead to the intended destination. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 15-45 min | 1-2 Tage | 1-4 h | 20-45 min |
Participantsdifferent | 1-3 | Based on research question | 1-5 | Based on research question |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Findability Metrics, Path Analysis, Revised IA | Context Diagram, Container Diagram, Component Diagram | Content groups, Label set, IA hypotheses |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | Information architectureNavigationFindability | ArchitectureCommunicationVisualization | Information architectureNavigationStructure |



