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 InterviewARID (Active Reviews for Intermediate Designs)Architecture Decision Record
| Criterion |  Product Discovery Opportunity Interview |  Architecture ARID (Active Reviews for Intermediate Designs) |  Architecture Architecture Decision Record |
|---|---|---|---|
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. | 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. | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. |
Complexitydifferent | Medium | Medium | Low |
Timedifferent | 30-60 min je Interview | 2–4 h review as a planning range; preparation and evaluation additional | 15-45 min |
Participantsdifferent | 5-12 Interviews | Designers, developers as users, and facilitation | 1-3 |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions | ADR File, Decision Log, Rationale |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureEngineeringFeedbackValidationTasks | ArchitectureRationaleDocumentationGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
