View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Architecture Architecture Decision Record |  Product Discovery Smoke Test |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable. | 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 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 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 | Medium | Low | Low | Medium |
Timedifferent | 30-240 min | 15-45 min | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 1-6 | 1-3 | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | ADR File, Decision Log, Rationale | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | ArchitectureRationaleDocumentationGovernance | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |