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 C4 Model |  Innovation Design Thinking |  Architecture arc42 |
|---|---|---|---|---|
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. | 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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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 | Medium | Low | High | Low |
Timedifferent | 1-2 h je Session | 1-4 h | 1 Tag bis mehrere Wochen | 1-2 Tage |
Participantsdifferent | Based on research question | 1-5 | 4-10 | 1-4 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Context Diagram, Container Diagram, Component Diagram | Problem Statement, Prototype, Test Learnings | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ValidationUXPrototype | ArchitectureCommunicationVisualization | InnovationPrototypeResearch | ArchitectureDocumentationCommunication |