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 Thinking |  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. | For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service. | 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 | High | Low | Low |
Timedifferent | 2–4 h review as a planning range; preparation and evaluation additional | 1 Tag bis mehrere Wochen | 20-35 min | 30-60 min |
Participantsdifferent | Designers, developers as users, and facilitation | 4-10 | 1-5 | 1-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Problem Statement, Prototype, Test Learnings | Test Card with a pre-set threshold | Completed Experiment Canvas, Success Metric |
Tagsno overlap | ArchitectureEngineeringFeedbackValidationTasks | InnovationPrototypeResearch | ExperimentsValidationDiscoveryHypothesis | ExperimentsValidationDiscoveryHypothesis |