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 Request for Comments |  Architecture C4 Model |
|---|---|---|---|
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 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. | 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 | Medium | Medium | Low |
Timedifferent | 1-2 h je Session | 1-3 Wochen vom Draft bis zur Entscheidung | 1-4 h |
Participantsdifferent | Based on research question | 3-20 Reviewer | 1-5 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Usability Issues, Severity List, Recommendations | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ValidationUXPrototype | ArchitectureDecisionAsyncGovernance | ArchitectureCommunicationVisualization |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
