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 Concierge MVP |  Product Discovery Fake Door Test |  Product Discovery Experiment Canvas |
|---|---|---|---|---|
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 an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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. | When experiments become unreadable after the fact, it arranges hypothesis, signal, and learning goal on a single canvas. It separates problem, assumption, solution, and evidence. The result is captured as a Completed Experiment Canvas and a Success Metric. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 Wochen | 1-5 Tage | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-10 Kunden | 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 | Concierge Learnings, Service Blueprint, MVP Risks | Click Data, Interest Signal, Learning Decision | Completed Experiment Canvas, Success Metric |
Tags1 shared | ArchitectureEngineeringFeedbackValidationTasks | MVPValidationServiceDiscovery | ValidationExperimentsDemandDiscovery | ExperimentsValidationDiscoveryHypothesis |