View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Constraint Analysis | ![]() Architecture ARID (Active Reviews for Intermediate Designs) | ![]() Product Discovery Test Card | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | 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 Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | 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 | 30-90 min | 2–4 h review as a planning range; preparation and evaluation additional | 20-35 min | 1-5 Tage |
Participantsdifferent | 2-8 | Designers, developers as users, and facilitation | 1-5 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Test Card with a pre-set threshold | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ConstraintsDecisionPlanningOptions | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsValidationDiscoveryHypothesis | ValidationExperimentsDemandDiscovery |



