View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Architecture arc42 |  Product Discovery Opportunity Solution Tree |  Architecture C4 Model |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 1-2 Tage | 1-2 h Setup, laufend | 1-4 h | 1-5 Tage |
Participantsdifferent | 1-4 | 2-6 | 1-5 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Opportunity Solution Tree, Experiment Backlog, Learning Log | Context Diagram, Container Diagram, Component Diagram | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ArchitectureDocumentationCommunication | DiscoveryOutcomesExperimentsOpportunity | ArchitectureCommunicationVisualization | ValidationExperimentsDemandDiscovery |