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 Time Blocking
Operations
Time Blocking
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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.With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure.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.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
LowLowMediumMedium
Timedifferent
1-2 h15-30 min Planung, laufend1-3 h1-3 h
Participantsdifferent
2-813-82-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeBlocked Calendar, Capacity View, Focus PlanContext Canvas, Glossary, Integration NotesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
PlanningTime managementFocus
Domain-Driven DesignBoundariesModeling
Domain-Driven DesignBoundariesStrategy
Add more methods