View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Smoke Test |  Facilitation Consensus Workshop |  Architecture Risk Storming |  Growth A/B Testing |
|---|---|---|---|---|
Purposedifferent | 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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time. | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | 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 | Medium | Low | High |
Timedifferent | 1-5 Tage | 1-3 h | 60-90 min | 1-4 Wochen |
Participantsdifferent | Nutzertraffic | 5-30 | 4-12 | 1-6 |
Formatdifferent | Async | Workshop | Workshop | Async |
Outputdifferent | Interest Metrics, Conversion Signal, Learning Note | Consensus Clusters, Theme Titles, Priority Areas | Annotated Diagram, Prioritized Risk List, Action Backlog | Experiment results, Decision log, Learning summary |
Tagsno overlap | ValidationExperimentsDemandGrowth | FacilitationConsensusWorkshopAlignment | RiskArchitectureWorkshopValidation | ExperimentsGrowthAnalyticsValidation |