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 |  Decision Making Pre-Mortem |  Product Discovery Smoke Test |  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. | In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures. | When demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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 | Low | Low | Medium |
Timedifferent | 1-3 h | 20–45 min | 1-5 Tage | 1-5 Tage |
Participantsdifferent | 2-8 | Small cross-functional group | Nutzertraffic | Nutzertraffic |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Risk list, Mitigation plan, Assumption log | Interest Metrics, Conversion Signal, Learning Note | Click Data, Interest Signal, Learning Decision |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | RiskDecisionFailurePlanning | ValidationExperimentsDemandGrowth | ValidationExperimentsDemandDiscovery |