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 Communication Canvas |  Product Discovery Problem Interview |  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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. | 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 | Medium | Medium | Low |
Timedifferent | 30-60 min je Interview | 60-120 min | 30-60 min je Interview | 1-2 Tage |
Participantsdifferent | 5-12 Interviews | 2-8 | 5-12 Interviews | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Problem Evidence, Risk Notes, Customer Segments | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureCommunicationStakeholdersCanvas | DiscoveryInterviewsValidation | ArchitectureDocumentationCommunication |