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 Affinity Diagramming |  Product Discovery Smoke Test |  Architecture arc42 |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | When research notes, feedback, or observations sit unconnected side by side, affinity diagramming sorts the raw material into solid themes. Many individual points turn into patterns that make decisions and opportunities clearer. | 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 | Low | Low | Low | High |
Timedifferent | 45–90 min | 1-5 Tage | 1-2 Tage | 1-4 Wochen |
Participantsdifferent | 3-10 | Nutzertraffic | 1-4 | 1-6 |
Formatdifferent | Workshop | Async | Workshop + async | Async |
Outputdifferent | Theme clusters, Insight statements, Opportunity areas | Interest Metrics, Conversion Signal, Learning Note | Architecture Document, Context View, Runtime View, Deployment View | Experiment results, Decision log, Learning summary |
Tagsno overlap | SynthesisQualitativeRoot cause | ValidationExperimentsDemandGrowth | ArchitectureDocumentationCommunication | ExperimentsGrowthAnalyticsValidation |