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 Request for Comments |  Architecture arc42 |  Architecture C4 Model |
|---|---|---|---|---|
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. | An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 20-45 min | 1-3 Wochen vom Draft bis zur Entscheidung | 1-2 Tage | 1-4 h |
Participantsdifferent | Based on research question | 3-20 Reviewer | 1-4 | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Content groups, Label set, IA hypotheses | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | Information architectureNavigationStructure | ArchitectureDecisionAsyncGovernance | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization |