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
Context Map workspace showing the question, observations, and next decision.
Domain Modeling
Context Map
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
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 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.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.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.
Complexitydifferent
MediumMediumHighLow
Timedifferent
1-3 h1-3 h1-4 h45-90 min
Participantsdifferent
3-122-83-82-8
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanContext Map, Integration Patterns, Boundary NotesChallenge Findings, Risk Register, Mitigation PlanAssumption List, Critical Assumptions, Learning Plan
Tagsno overlap
KnowledgeMappingRisk
Domain-Driven DesignBoundariesStrategy
RiskDecisionSensemaking
AssumptionsRiskDecisionDiscovery
Add more methods