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 |  Operations Root Cause Tree Analysis |  Architecture arc42 |
|---|---|---|---|---|
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. | For a problem with several suspected causes, the method builds a causal structure instead of a mere list. It makes visible how causes connect and where the strongest points of leverage lie. | 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 30-60 min je Interview | 15-45 min | 1-3 h | 1-2 Tage |
Participantsdifferent | 5-12 Interviews | 1-3 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | ADR File, Decision Log, Rationale | Cause Tree, Evidence Notes, Countermeasures | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureRationaleDocumentationGovernance | Root causeTreeIncidentQuality | ArchitectureDocumentationCommunication |