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 |  Product Discovery Smoke Test |  Architecture arc42 |  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. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 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 | Low | High |
Timedifferent | 1-2 h je Session | 1-5 Tage | 1-2 Tage | 1-4 Wochen |
Participantsdifferent | Based on research question | Nutzertraffic | 1-4 | 1-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Usability Issues, Severity List, Recommendations | Interest Metrics, Conversion Signal, Learning Note | Architecture Document, Context View, Runtime View, Deployment View | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationUXPrototype | ValidationExperimentsDemandGrowth | ArchitectureDocumentationCommunication | ExperimentsGrowthAnalyticsValidation |