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
Paper illustration of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
A paper-based illustration representing Event Modeling with its core stages and visible working result.
Knowledge Modeling
Event Modeling
A paper-based illustration representing Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Purposedifferent
Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy.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.When a business context is still loosely outlined, it shapes language, responsibility, and integration space. It clarifies what belongs together and where a boundary needs to hold.
Complexitydifferent
HighMediumMedium
Timedifferent
Half day2-6 h1-3 h
Participantsdifferent
3-122-83-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Leverage Map, Action StrategyEvent Model, UI Flow, Commands, Read ModelsContext Canvas, Glossary, Integration Notes
Tagsno overlap
Systems thinkingChangeStrategy
EventsBlueprintDomain-Driven DesignBehavior
Domain-Driven DesignBoundariesModeling
Add more methods

Often compared together

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

Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for Domain Context Map
Domain Modeling
Domain 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