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
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Purposedifferent
When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments.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.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.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
1-3 h1-4 h1-3 h1-3 h
Participantsdifferent
1-83-83-102-8
Formatdifferent
Workshop + asyncWorkshopWorkshopWorkshop + async
Outputdifferent
Argument Map, Evidence Gaps, Decision RationaleChallenge Findings, Risk Register, Mitigation PlanDomain Context Map, Boundary Notes, Ownership MapContext Map, Integration Patterns, Boundary Notes
Tagsno overlap
SensemakingDecisionRationale
RiskDecisionSensemaking
Domain-Driven DesignContextBoundaries
Domain-Driven DesignBoundariesStrategy
Add more methods