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 Opportunity Interview |  Architecture arc42 |  Architecture ARID (Active Reviews for Intermediate Designs) |  Product Discovery Problem Interview |
|---|---|---|---|---|
Purposedifferent | When opportunities are still hidden behind signals of need, it structures conversations around needs and obstacles. It looks for patterns that lead to new product opportunities. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 30-60 min je Interview | 1-2 Tage | 2–4 h review as a planning range; preparation and evaluation additional | 30-60 min je Interview |
Participantsdifferent | 5-12 Interviews | 1-4 | Designers, developers as users, and facilitation | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Architecture Document, Context View, Runtime View, Deployment View | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureDocumentationCommunication | ArchitectureEngineeringFeedbackValidationTasks | DiscoveryInterviewsValidation |