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
A paper tomato timer connects a focus task, short breaks and a work record.
Operations
Pomodoro Technique
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
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.For easily distracted solo work, the method sets clear time boundaries for concentrated work. It protects attention when large tasks would otherwise fall apart into small avoidance moves.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 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 h25 min Zyklen1-3 h1-3 h
Participantsdifferent
2-813-102-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeFocus Sessions, Task Progress, Interruption NotesDomain Context Map, Boundary Notes, Ownership MapContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
FocusTime managementProductivityExecution
Domain-Driven DesignContextBoundaries
Domain-Driven DesignBoundariesStrategy
Add more methods