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 of a Concept Map with concepts and labelled links
Knowledge Modeling
Concept Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Purposedifferent
Concept Mapping arranges terms and relationships in a network that makes subject-matter connections tangible. It fits when a topic needs to be understood structurally rather than linearly.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.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.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
MediumLowLowHigh
Timedifferent
1-2 h30 min Setup, dann laufend45-90 min1-4 h
Participantsdifferent
1-81-3 maintaining, briefing for everyone2-83-8
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop
Outputdifferent
Concept Map, Relationship Labels, Knowledge GapsRAID Log, Status Report SourceAssumption List, Critical Assumptions, Learning PlanChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
KnowledgeConceptsMappingSensemaking
RiskTrackingStakeholdersGovernance
AssumptionsRiskDecisionDiscovery
RiskDecisionSensemaking
Add more methods