View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Problem Interview |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Test Card |
|---|---|---|---|
Purposedifferent | When the picture of the problem still needs to become solid, it asks about real situations and consequences. It separates genuine suffering from mere interest in a solution. | 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. | The Test Card turns a critical assumption into a testable claim and specifies in advance which result counts as success. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 30-60 min je Interview | 2–4 h review as a planning range; preparation and evaluation additional | 20-35 min |
Participantsdifferent | 5-12 Interviews | Designers, developers as users, and facilitation | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Problem Evidence, Risk Notes, Customer Segments | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Test Card with a pre-set threshold |
Tags1 shared | DiscoveryInterviewsValidation | ArchitectureEngineeringFeedbackValidationTasks | ExperimentsValidationDiscoveryHypothesis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
