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 arc42 |  Innovation Design Sprint |  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. | 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. | When the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. | 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 | Low | High | Low |
Timedifferent | 1-2 h je Session | 1-2 Tage | 4-5 Tage | 1-4 h |
Participantsdifferent | Based on research question | 1-4 | 5-8 | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Architecture Document, Context View, Runtime View, Deployment View | Prototype, Test Findings, Decision Rationale | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | ValidationUXPrototype | ArchitectureDocumentationCommunication | Design sprintPrototypeValidationInnovation | ArchitectureCommunicationVisualization |