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) |  Agile Example Mapping |  Product Discovery Learning Card |  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 a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. | 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 | Low | Low | Medium |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min | 25-40 min | 1-5 Tage |
Participantsdifferent | Designers, developers as users, and facilitation | 3-7 | 1-5 | 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 | Example Map, Acceptance Criteria, Open Questions | Learning Card with evidence and next action | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | Behavior-Driven DevelopmentRequirementsExamplesRefinement | ExperimentsValidationDiscoveryLearning | ValidationExperimentsDemandDiscovery |