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 Quality Attribute Workshop |  UX Research Usability Testing |  Product Discovery Smoke Test |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | A Quality Attribute Workshop translates quality requirements into concrete scenarios and architecture impulses. The method brings product, engineering, and operations to the same view of desired properties. | 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. | 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 | Medium | Low | High |
Timedifferent | 2-4 h | 1-2 h je Session | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 5-15 | Based on research question | Nutzertraffic | 1-6 |
Formatdifferent | Workshop | Workshop + async | Async | Async |
Outputdifferent | Quality Scenarios, Priority List, Architecture Concerns | Usability Issues, Severity List, Recommendations | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | RequirementsArchitectureWorkshop | ValidationUXPrototype | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |