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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
A paper-based illustration representing Domain Storytelling with its core stages and visible working result.
Knowledge Modeling
Domain Storytelling
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Purposedifferent
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.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.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.When a domain model and its associated contexts need to be thought through together, it creates a shared overview. It connects the business view and organizational boundary into a readable whole.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-3 h1-2 h2-4 h1-3 h
Participantsdifferent
2-82-83-123-10
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop
Outputdifferent
Context Map, Integration Patterns, Boundary NotesDomain Story, Glossary Notes, Process Narrative7S Assessment, Alignment Gaps, Change ActionsDomain Context Map, Boundary Notes, Ownership Map
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
KnowledgeDomain-Driven DesignProcess
OrganizationStrategyAlignmentChange
Domain-Driven DesignContextBoundaries
Add more methods