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 Smoke Test | ![]() Business Strategy Value Chain Analysis |
|---|---|---|---|
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 demand only needs to be roughly verified, it tests interest with minimal effort. It measures whether people would take a next step at all. | 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. |
Complexitydifferent | Medium | Low | High |
Timedifferent | 1-3 h | 1-5 Tage | Half day |
Participantsdifferent | 2-8 | Nutzertraffic | 3-8 |
Formatdifferent | Workshop + async | Async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Interest Metrics, Conversion Signal, Learning Note | Value Chain Map, Lever List |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | ValidationExperimentsDemandGrowth | StrategyBusiness modelDiagnosisAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






