View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Domain Modeling Context Map |  Product Discovery Concierge MVP |  Product Discovery Learning Card |  Product Discovery Fake Door Test |
|---|---|---|---|---|
Purposedifferent | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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. | The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible. | 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 | Medium | Medium | Low | Medium |
Timedifferent | 1-3 h | 1-4 Wochen | 25-40 min | 1-5 Tage |
Participantsdifferent | 2-8 | 3-10 Kunden | 1-5 | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Concierge Learnings, Service Blueprint, MVP Risks | Learning Card with evidence and next action | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | MVPValidationServiceDiscovery | ExperimentsValidationDiscoveryLearning | ValidationExperimentsDemandDiscovery |