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 arc42 |  Architecture C4 Model |  Product Discovery Problem Interview |
|---|---|---|---|---|
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. | 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 C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-60 min je Interview | 1-2 Tage | 1-4 h | 30-60 min je Interview |
Participantsdifferent | 5-12 Interviews | 1-4 | 1-5 | 5-12 Interviews |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Architecture Document, Context View, Runtime View, Deployment View | Context Diagram, Container Diagram, Component Diagram | Problem Evidence, Risk Notes, Customer Segments |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureDocumentationCommunication | ArchitectureCommunicationVisualization | DiscoveryInterviewsValidation |