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 RecordFake Door TestARID (Active Reviews for Intermediate Designs)Learning Card
| Criterion |  Architecture Architecture Decision Record |  Product Discovery Fake Door Test |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Learning Card |
|---|---|---|---|---|
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 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. | 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 15-45 min | 1-5 Tage | 2–4 h review as a planning range; preparation and evaluation additional | 25-40 min |
Participantsdifferent | 1-3 | Nutzertraffic | Designers, developers as users, and facilitation | 1-5 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Click Data, Interest Signal, Learning Decision | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Learning Card with evidence and next action |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | ValidationExperimentsDemandDiscovery | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsValidationDiscoveryLearning |