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
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 of Leverage Points with its method-specific working model.
Systems Thinking
Leverage Points
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.When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries.Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins.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.
Complexitydifferent
LowMediumMediumHigh
Timedifferent
1-2 h1-3 h1-3 hHalf day
Participantsdifferent
2-82-83-123-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeContext Map, Integration Patterns, Boundary NotesSystem Map, Dependencies, Leverage PointsLeverage Map, Action Strategy
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
Domain-Driven DesignBoundariesStrategy
Systems thinkingMappingBoundariesChange
Systems thinkingChangeStrategy
Add more methods