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 PERT Estimation | ![]() 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. | On complex initiatives, a plain average tends to understate just how uncertain the outcome really is. It separates options, evaluation criteria, and open risks. The result is captured as a PERT Estimate, Expected Value, and Risk Notes. | 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 | Medium | High |
Timedifferent | 1-3 h | 15-45 min | Half day |
Participantsdifferent | 2-8 | 1-8 | 3-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | PERT Estimate, Expected Value, Risk Notes | Value Chain Map, Lever List |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | EstimationUncertaintyRisk | StrategyBusiness modelDiagnosisAnalysis |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






