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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
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 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.With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots.When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions.
Complexitydifferent
LowMediumMediumLow
Timedifferent
1-2 h1-3 h1-3 h30-120 min
Participantsdifferent
2-82-83-102-6
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeContext Map, Integration Patterns, Boundary NotesProcess Map, Handoff List, Improvement BacklogObservation Notes, Improvement Ideas
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Domain-Driven DesignBoundariesStrategy
ProcessOperationsImprovement
LeanObservationProcessOperations
Add more methods