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
EventStorming on a long working surface: colored event cards form a business flow, friction points are marked, and a boundary separates different areas of responsibility.
Domain Modeling
EventStorming
Paper illustration for Time Blocking
Operations
Time Blocking
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Purposedifferent
When a domain consists of many events, rules, and states, it creates a shared modeling space for the team. It bundles language, flows, and boundaries before domain knowledge fragments into siloed views.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 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.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
MediumLowMediumMedium
Timedifferent
2-8 h15-30 min Planung, laufend1-3 h1-3 h
Participantsdifferent
5-1213-103-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsBlocked Calendar, Capacity View, Focus PlanDomain Context Map, Boundary Notes, Ownership MapContext Canvas, Glossary, Integration Notes
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
PlanningTime managementFocus
Domain-Driven DesignContextBoundaries
Domain-Driven DesignBoundariesModeling
Add more methods