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 C4 Model |  Product Discovery Opportunity Interview |  Product Discovery Assumption Mapping |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 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. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. | 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 | Medium | Medium |
Timedifferent | 1-4 h | 30-60 min je Interview | 45-60 min | 1-5 Tage |
Participantsdifferent | 1-5 | 5-12 Interviews | 2-8 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Interview Notes, Opportunity Themes, Customer Quotes | Assumption map, Test backlog, Risk ranking | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | ArchitectureCommunicationVisualization | DiscoveryInterviewsOpportunityCustomer | AssumptionsRiskExperimentsValidation | ValidationExperimentsDemandDiscovery |