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 |  Operations Root Cause Tree Analysis |  Architecture arc42 |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | 1-3 h | 1-2 Tage | 60-120 min |
Participantsdifferent | 5-12 Interviews | 2-8 | 1-4 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Cause Tree, Evidence Notes, Countermeasures | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | Root causeTreeIncidentQuality | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas |