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 Design Sprint |  Product Discovery Concierge MVP |  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 the product question is unclear and time pressure is high, the method takes a team from an open idea to a testable solution. It connects problem understanding, decision, and learning in one compact format, lowering the risk of spending a lot of energy on a mere guess. | 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. |
Complexitydifferent | Medium | High | Medium | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 4-5 Tage | 1-4 Wochen | 1-5 Tage |
Participantsdifferent | Designers, developers as users, and facilitation | 5-8 | 3-10 Kunden | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Prototype, Test Findings, Decision Rationale | Concierge Learnings, Service Blueprint, MVP Risks | Click Data, Interest Signal, Learning Decision |
Tags1 shared | ArchitectureEngineeringFeedbackValidationTasks | Design sprintPrototypeValidationInnovation | MVPValidationServiceDiscovery | ValidationExperimentsDemandDiscovery |