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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Purposedifferent
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.Event Modeling connects business workflows with commands, events, and views into one coherent mental model. It helps design behavior, UI, and technical slices from the same underlying logic.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.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 h30-120 min2-6 h1-2 h
Participantsdifferent
3-102-62-82-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Process Map, Handoff List, Improvement BacklogObservation Notes, Improvement IdeasEvent Model, UI Flow, Commands, Read ModelsDomain Story, Glossary Notes, Process Narrative
Tagsno overlap
ProcessOperationsImprovement
LeanObservationProcessOperations
EventsBlueprintDomain-Driven DesignBehavior
KnowledgeDomain-Driven DesignProcess
Add more methods