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 Architecture Decision Record |  Product Discovery Smoke Test |  Architecture arc42 |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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. | 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 | Low | Low | Low | Medium |
Timedifferent | 15-45 min | 1-5 Tage | 1-2 Tage | 1-5 Tage |
Participantsdifferent | 1-3 | Nutzertraffic | 1-4 | Nutzertraffic |
Formatdifferent | Async | Async | Workshop + async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Interest Metrics, Conversion Signal, Learning Note | Architecture Document, Context View, Runtime View, Deployment View | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ValidationExperimentsDemandGrowth | ArchitectureDocumentationCommunication | ValidationExperimentsDemandDiscovery |