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
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.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.In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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 min20–45 min1-3 h
Participantsdifferent
3-101-6Small cross-functional group2-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Domain Context Map, Boundary Notes, Ownership MapDecision Tree, Option Map, Assumption ListRisk list, Mitigation plan, Assumption logContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Domain-Driven DesignContextBoundaries
DecisionTreeOptions
RiskDecisionFailurePlanning
Domain-Driven DesignBoundariesStrategy
Add more methods