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
Paper illustration of GIST Planning with its method-specific working model.
Product Strategy
GIST Planning
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.GIST Planning helps clarify target groups, value, goals, and priorities. It links customer value, product logic, and decision priorities, and captures the result as goals, an idea bank, and a step-project list.
Complexitydifferent
LowMediumMedium
Timedifferent
1-2 h2-6 hWochen bis Monate je Goal
Participantsdifferent
2-82-83-10
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeEvent Model, UI Flow, Commands, Read ModelsGoals, Idea bank, Step-project list, Tasks, Learning reports
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
EventsBlueprintDomain-Driven DesignBehavior
RoadmapOutcomesPlanningExperiments
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
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 branching tree with an outcome at its root, customer opportunities, solution options and small experiment cards.
Product Discovery
Opportunity Solution Tree