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 |  Knowledge Modeling Concept Mapping |  Product Discovery Problem Interview |  Knowledge Modeling Knowledge 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. | Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly. | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 30-60 min je Interview | 1-2 h | 30-60 min je Interview | 1-3 h |
Participantsdifferent | 5-12 Interviews | 1-8 | 5-12 Interviews | 3-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Interview Notes, Opportunity Themes, Customer Quotes | Concept Map, Relationship Labels, Knowledge Gaps | Problem Evidence, Risk Notes, Customer Segments | Knowledge Map, Critical Knowledge Areas, Transfer Plan |
Tagsno overlap | DiscoveryInterviewsOpportunityCustomer | KnowledgeConceptsMappingSensemaking | DiscoveryInterviewsValidation | KnowledgeMappingRisk |