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-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
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.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.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.
Complexitydifferent
LowMediumMedium
Timedifferent
1-2 h2-6 h1-3 h
Participantssame
2-82-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeEvent Model, UI Flow, Commands, Read ModelsGap Matrix, Action Plan, Risk Notes
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
EventsBlueprintDomain-Driven DesignBehavior
StrategyAnalysisPlanning
Add more methods

Often compared together

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

Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
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 of a six-field PESTLE grid
Business Strategy
PESTLE Analysis