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 Architecture Decision Record | ![]() UX Research Usability Testing | ![]() Innovation Design Thinking |
|---|---|---|---|
Purposedifferent | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 15-45 min | 1-2 h je Session | 1 Tag bis mehrere Wochen |
Participantsdifferent | 1-3 | Based on research question | 4-10 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | ADR File, Decision Log, Rationale | Usability Issues, Severity List, Recommendations | Problem Statement, Prototype, Test Learnings |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ValidationUXPrototype | InnovationPrototypeResearch |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






