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 | ![]() Facilitation Problem Framing Workshop |
|---|---|---|---|
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. | When a team works on symptoms but the real question stays fuzzy, a Problem Framing Workshop sharpens the view of the right problem. It separates observation, interpretation, and target picture from each other. |
Complexitydifferent | Medium | Low | Low |
Timedifferent | 1-3 h | 45-90 min | 60-120 min |
Participantsdifferent | 2-8 | 2-8 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Context Map, Integration Patterns, Boundary Notes | Assumption List, Critical Assumptions, Learning Plan | Problem Statement, Scope Boundaries, Assumption List, Next Analysis Questions |
Tagsno overlap | Domain-Driven DesignBoundariesStrategy | AssumptionsRiskDecisionDiscovery | FacilitationAlignmentDiscovery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






