View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Architecture Decision RecordARID (Active Reviews for Intermediate Designs)Smoke TestFake Door Test
| Criterion |  Architecture Architecture Decision Record |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Smoke Test |  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. | ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification. | 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 | Medium | Low | Medium |
Timedifferent | 15-45 min | 2–4 h review as a planning range; preparation and evaluation additional | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 1-3 | Designers, developers as users, and facilitation | Nutzertraffic | Nutzertraffic |
Formatdifferent | Async | Workshop + async | Async | Async |
Outputdifferent | ADR File, Decision Log, Rationale | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ArchitectureEngineeringFeedbackValidationTasks | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |