View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Opportunity InterviewProblem InterviewATAM (Architecture Tradeoff Analysis Method)ARID (Active Reviews for Intermediate Designs)
| Criterion |  Product Discovery Opportunity Interview |  Product Discovery Problem Interview |  Architecture ATAM (Architecture Tradeoff Analysis Method) |  Architecture ARID (Active Reviews for Intermediate Designs) |
|---|---|---|---|---|
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. | 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. | ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation. | 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. |
Complexitydifferent | Medium | Medium | High | Medium |
Timedifferent | 30-60 min je Interview | 30-60 min je Interview | Several meetings plus preparation and analysis; total effort depends on scope | 2–4 h review as a planning range; preparation and evaluation additional |
Participantsdifferent | 5-12 Interviews | 5-12 Interviews | Evaluation team, architects, and relevant stakeholders | Designers, developers as users, and facilitation |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Problem Evidence, Risk Notes, Customer Segments | Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | DiscoveryInterviewsValidation | ArchitectureQualityRiskTradeoffsStakeholders | ArchitectureEngineeringFeedbackValidationTasks |