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 Strategy Counter Metrics | ![]() Architecture Architecture Decision Record | ![]() Product Discovery Smoke Test | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When a headline metric could mask side effects, it adds guardrail signals against unwanted outcomes. It connects customer value, product logic, and decision priorities. The result is captured as a counter-metric list and guardrail definitions. | 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 | Low | Low | Low | Medium |
Timedifferent | 30-60 min | 15-45 min | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 2-6 | 1-3 | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Async | Async |
Outputdifferent | Counter Metric List, Guardrail Definitions | ADR File, Decision Log, Rationale | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | MetricsMeasurementStrategyExperiments | ArchitectureRationaleDocumentationGovernance | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |



