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 Solution Tree |  Architecture arc42 |  Product Discovery Opportunity Interview |  Architecture C4 Model |
|---|---|---|---|---|
Purposedifferent | When discovery keeps swinging between goals, ideas, and learning loops, it creates clear steering logic. It connects the desired outcome, opportunities, and experiments into a legible structure. | 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. | 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 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. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-2 h Setup, laufend | 1-2 Tage | 30-60 min je Interview | 1-4 h |
Participantsdifferent | 2-6 | 1-4 | 5-12 Interviews | 1-5 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Opportunity Solution Tree, Experiment Backlog, Learning Log | Architecture Document, Context View, Runtime View, Deployment View | Interview Notes, Opportunity Themes, Customer Quotes | Context Diagram, Container Diagram, Component Diagram |
Tagsno overlap | DiscoveryOutcomesExperimentsOpportunity | ArchitectureDocumentationCommunication | DiscoveryInterviewsOpportunityCustomer | ArchitectureCommunicationVisualization |