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 Outcome-Driven Innovation |  Architecture Architecture Decision Record |  Growth A/B Testing |  Product Discovery Smoke Test |
|---|---|---|---|---|
Purposedifferent | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | 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. |
Complexitydifferent | High | Low | High | Low |
Timedifferent | Mehrere Wochen | 15-45 min | 1-4 Wochen | 1-5 Tage |
Participantsdifferent | 2-6 researchers plus sample | 1-3 | 1-6 | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | ADR File, Decision Log, Rationale | Experiment results, Decision log, Learning summary | Interest Metrics, Conversion Signal, Learning Note |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureRationaleDocumentationGovernance | ExperimentsGrowthAnalyticsValidation | ValidationExperimentsDemandGrowth |