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
Paper illustration for Change Analysis.
Operations
Change Analysis
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
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.For a deviation after a change, the method isolates the influence of the altered condition. It narrows down which differences are relevant and which are just accompanying noise.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.Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
1-2 h45-120 min1-3 h1-2 h
Participantsdifferent
2-82-63-121-8
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Domain Story, Glossary Notes, Process NarrativeChange Matrix, Cause Hypotheses, Validation Questions, Action ListSystem Map, Dependencies, Leverage PointsConcept Map, Relationship Labels, Knowledge Gaps
Tagsno overlap
KnowledgeDomain-Driven DesignProcess
ChangeRoot causeTroubleshootingComparison
Systems thinkingMappingBoundariesChange
KnowledgeConceptsMappingSensemaking
Add more methods