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 Architecture Decision Record | ![]() Growth A/B Testing |
|---|---|---|---|
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 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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 1-2 h je Session | 15-45 min | 1-4 Wochen |
Participantsdifferent | Based on research question | 1-3 | 1-6 |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | Usability Issues, Severity List, Recommendations | ADR File, Decision Log, Rationale | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationUXPrototype | ArchitectureRationaleDocumentationGovernance | ExperimentsGrowthAnalyticsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






