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 Assumption Surfacing |  Decision Making Trade-off Analysis |  Product Discovery Assumption Mapping |
|---|---|---|---|---|
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. | Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it. | With limited resources, quality, speed, cost, and risk almost always compete with each other. Trade-off Analysis makes these tensions explicit and prevents decisions from producing hidden side effects. | When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first. |
Complexitydifferent | Medium | Low | Medium | Medium |
Timedifferent | 1-3 h | 45-90 min | 45-120 min | 45-60 min |
Participantssame | 2-8 | 2-8 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Assumption List, Critical Assumptions, Learning Plan | Trade-off Matrix, Criteria List, Decision Rationale, Accepted Downsides | Assumption map, Test backlog, Risk ranking |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | AssumptionsRiskDecisionDiscovery | TradeoffsDecisionCriteriaOptions | AssumptionsRiskExperimentsValidation |