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 arc42 |  UX Research Usability Testing |  Innovation Design Sprint |  Architecture Architecture Decision Record |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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. | 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. |
Complexitydifferent | Low | Medium | High | Low |
Timedifferent | 1-2 Tage | 1-2 h je Session | 4-5 Tage | 15-45 min |
Participantsdifferent | 1-4 | Based on research question | 5-8 | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Usability Issues, Severity List, Recommendations | Prototype, Test Findings, Decision Rationale | ADR File, Decision Log, Rationale |
Tagsno overlap | ArchitectureDocumentationCommunication | ValidationUXPrototype | Design sprintPrototypeValidationInnovation | ArchitectureRationaleDocumentationGovernance |