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 Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Purposedifferent
Domain Storytelling translates domain knowledge into a shared narrative of actors, objects, and workflows. It is especially useful when language, rules, and process understanding must be tightly connected.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.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.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.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 h1-3 h1-3 h1-3 h
Participantsdifferent
2-81-82-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeArgument Map, Evidence Gaps, Decision RationaleContext Map, Integration Patterns, Boundary NotesContext Canvas, Glossary, Integration Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
SensemakingDecisionRationale
Domain-Driven DesignBoundariesStrategy
Domain-Driven DesignBoundariesModeling
Add more methods