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 Architecture Decision Record |  Delivery RAID Log |
|---|---|---|---|
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. | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 30-60 min je Interview | 15-45 min | 30 min Setup, dann laufend |
Participantsdifferent | 5-12 Interviews | 1-3 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Async | Async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | ADR File, Decision Log, Rationale | RAID Log, Status Report Source |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureRationaleDocumentationGovernance | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
