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 Bounded Context Canvas with its core stages and visible working result.
Domain Modeling
Bounded Context Canvas
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
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.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.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.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.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 h1-3 h15-60 min je Zyklus1-3 h
Participantsdifferent
3-83-121-82-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Canvas, Glossary, Integration NotesSystem Map, Dependencies, Leverage PointsSituation Assessment, Decision Loop, Action UpdatesContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
Domain-Driven DesignBoundariesModeling
Systems thinkingMappingBoundariesChange
DecisionChangeLearningStrategy
Domain-Driven DesignBoundariesStrategy
Add more methods