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) |  Decision Making Red Teaming |  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 strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | 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 | High | Medium | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1-4 h | 1-5 Tage | 25-40 min |
Participantsdifferent | Designers, developers as users, and facilitation | 3-8 | Nutzertraffic | 1-5 |
Formatdifferent | Workshop + async | Workshop | Async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Challenge Findings, Risk Register, Mitigation Plan | Click Data, Interest Signal, Learning Decision | Learning Card with evidence and next action |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | RiskDecisionSensemaking | ValidationExperimentsDemandDiscovery | ExperimentsValidationDiscoveryLearning |