View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Knowledge Modeling Concept Mapping | ![]() UX Research Customer Journey Mapping | ![]() Product Discovery Concierge MVP | ![]() Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | 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 a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately. | When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution. | 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. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | 1-2 h | 2-4 h | 1-4 Wochen | 1-5 Tage |
Participantsdifferent | 1-8 | 4-10 | 3-10 Kunden | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Async |
Outputdifferent | Concept Map, Relationship Labels, Knowledge Gaps | Journey Map, Pain-point List, Opportunity Backlog | Concierge Learnings, Service Blueprint, MVP Risks | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | KnowledgeConceptsMappingSensemaking | JourneyServiceService design | MVPValidationServiceDiscovery | ValidationExperimentsDemandDiscovery |



