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 |  Product Discovery Smoke Test |  Architecture arc42 |  Product Discovery Fake Door 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. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Mehrere Wochen | 1-5 Tage | 1-2 Tage | 1-5 Tage |
Participantsdifferent | 2-6 researchers plus sample | Nutzertraffic | 1-4 | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Interest Metrics, Conversion Signal, Learning Note | Architecture Document, Context View, Runtime View, Deployment View | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ValidationExperimentsDemandGrowth | ArchitectureDocumentationCommunication | ValidationExperimentsDemandDiscovery |