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) | ![]() Innovation Lean Startup | ![]() Product Discovery Fake Door Test | ![]() Product Discovery Learning Card |
|---|---|---|---|---|
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. | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Wochen bis Monate je Lernzyklus | 1-5 Tage | 25-40 min |
Participantsdifferent | Designers, developers as users, and facilitation | 2-8 | Nutzertraffic | 1-5 |
Formatdifferent | Workshop + async | Workshop + async | Async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Click Data, Interest Signal, Learning Decision | Learning Card with evidence and next action |
Tags1 shared | ArchitectureEngineeringFeedbackValidationTasks | LeanStartupValidationMVP | ValidationExperimentsDemandDiscovery | ExperimentsValidationDiscoveryLearning |



