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 Pretotyping |  Product Discovery Test Card |  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. | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. | 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 | Low | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | Stunden bis wenige Tage | 20-35 min | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 1-4 | 1-5 | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Test Card with a pre-set threshold | Completed Experiment Canvas, Success Metric |
Tags1 shared | ArchitectureEngineeringFeedbackValidationTasks | ValidationDemandMVP | ExperimentsValidationDiscoveryHypothesis | ExperimentsValidationDiscoveryHypothesis |