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
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for OODA Loop.
Decision Making
OODA Loop
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.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.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.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.
Complexitydifferent
MediumMediumLowMedium
Timedifferent
1-3 h1-3 h45-90 min15-60 min je Zyklus
Participantsdifferent
2-83-122-81-8
Formatsame
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Context Map, Integration Patterns, Boundary NotesSystem Map, Dependencies, Leverage PointsAssumption List, Critical Assumptions, Learning PlanSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
Domain-Driven DesignBoundariesStrategy
Systems thinkingMappingBoundariesChange
AssumptionsRiskDecisionDiscovery
DecisionChangeLearningStrategy
Add more methods