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 Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Paper illustration for Domain Context Map
Domain Modeling
Domain Context Map
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Purposedifferent
Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable.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 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.
Complexitydifferent
MediumMediumMediumHigh
Timedifferent
1-3 h1-3 h1-3 h1-4 h
Participantsdifferent
3-123-101-83-8
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanDomain Context Map, Boundary Notes, Ownership MapArgument Map, Evidence Gaps, Decision RationaleChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
KnowledgeMappingRisk
Domain-Driven DesignContextBoundaries
SensemakingDecisionRationale
RiskDecisionSensemaking
Add more methods