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
Process Mapping method illustration showing its working structure
Operations
Process Mapping
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 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.
Complexitysame
MediumMedium
Timedifferent
2-8 h1-3 h
Participantsdifferent
5-123-10
Formatsame
WorkshopWorkshop
Outputdifferent
Event Timeline, Ubiquitous Language, Boundaries, Open QuestionsProcess Map, Handoff List, Improvement Backlog
Tagsno overlap
Domain-Driven DesignEventsDiscoveryWorkshop
ProcessOperationsImprovement
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of a review with planned work, actual event sequence, comparison, and assigned improvement actions.
Operations
After-Action Review
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Gemba Walk workspace showing the question, observations, and next decision.
Operations
Gemba Walk