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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.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
MediumLowMediumHigh
Timedifferent
1-3 h30 min Setup, dann laufend1-3 h1-4 h
Participantsdifferent
3-121-3 maintaining, briefing for everyone1-83-8
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanRAID Log, Status Report SourceArgument Map, Evidence Gaps, Decision RationaleChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
KnowledgeMappingRisk
RiskTrackingStakeholdersGovernance
SensemakingDecisionRationale
RiskDecisionSensemaking
Add more methods