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 Risk Storming |  Product Discovery Smoke Test |  Business Strategy Business Model Stress Test |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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 | Low | Low | High | Medium |
Timedifferent | 60-90 min | 1-5 Tage | Half day | 1-5 Tage |
Participantsdifferent | 4-12 | Nutzertraffic | 3-8 | Nutzertraffic |
Formatdifferent | Workshop | Async | Workshop | Async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Interest Metrics, Conversion Signal, Learning Note | Stress Test Report, Action Plan per Scenario | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | RiskArchitectureWorkshopValidation | ValidationExperimentsDemandGrowth | StrategyBusiness modelRiskDiagnosis | ValidationExperimentsDemandDiscovery |