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 C4 Model | ![]() Product Discovery Assumption Mapping |
|---|---|---|---|
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 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 assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 30-60 min je Interview | 1-4 h | 45-60 min |
Participantsdifferent | 5-12 Interviews | 1-5 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Context Diagram, Container Diagram, Component Diagram | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | ArchitectureCommunicationVisualization | AssumptionsRiskExperimentsValidation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






