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
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.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.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
MediumLowHighLow
Timedifferent
1-3 h30 min Setup, dann laufend1-4 h45-90 min
Participantsdifferent
3-121-3 maintaining, briefing for everyone3-82-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop + async
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanRAID Log, Status Report SourceChallenge Findings, Risk Register, Mitigation PlanAssumption List, Critical Assumptions, Learning Plan
Tags1 shared
KnowledgeMappingRisk
RiskTrackingStakeholdersGovernance
RiskDecisionSensemaking
AssumptionsRiskDecisionDiscovery
Add more methods