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 ARID (Active Reviews for Intermediate Designs) |  Product Discovery Smoke Test |  Knowledge Modeling Shape-First Modeling |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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. | Shape-First Modeling defines data quality through shapes before implementation or integration frays at the edges. The approach fits when validation and data contracts should be part of the design from the start. | 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 | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-5 Tage | Halber Tag pro Domain Slice | 1-5 Tage |
Participantsdifferent | Designers, developers as users, and facilitation | Nutzertraffic | 1-4 | Nutzertraffic |
Formatdifferent | Workshop + async | Async | Workshop + async | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Interest Metrics, Conversion Signal, Learning Note | SHACL or ShEx Shapes, Validation Reports, Data Contracts, Shape Documentation | Click Data, Interest Signal, Learning Decision |
Tags1 shared | ArchitectureEngineeringFeedbackValidationTasks | ValidationExperimentsDemandGrowth | Knowledge graphValidationSemantic | ValidationExperimentsDemandDiscovery |