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 |  Business Strategy Value Chain Analysis |  Product Discovery Smoke Test |  Growth A/B Testing |
|---|---|---|---|---|
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. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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 two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects. |
Complexitydifferent | Medium | High | Low | High |
Timedifferent | 1-3 h | Half day | 1-5 Tage | 1-4 Wochen |
Participantsdifferent | 2-8 | 3-8 | Nutzertraffic | 1-6 |
Formatdifferent | Workshop + async | Workshop | Async | Async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Value Chain Map, Lever List | Interest Metrics, Conversion Signal, Learning Note | Experiment results, Decision log, Learning summary |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | StrategyBusiness modelDiagnosisAnalysis | ValidationExperimentsDemandGrowth | ExperimentsGrowthAnalyticsValidation |