methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.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 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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h30-90 min45-90 min1-3 h
Participantsdifferent
3-81-62-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesDecision Tree, Option Map, Assumption ListAssumption List, Critical Assumptions, Learning PlanContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Domain-Driven DesignBoundariesModeling
DecisionTreeOptions
AssumptionsRiskDecisionDiscovery
Domain-Driven DesignBoundariesStrategy
Add more methods