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 Soft Systems Methodology.
Systems Thinking
Soft Systems Methodology
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.Soft Systems Methodology helps explore unclear or politically charged problems systematically. Instead of forcing a quick answer, the method builds a shared understanding of perspectives and room for action.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
MediumLowHighHigh
Timedifferent
1-3 h30 min Setup, dann laufend0.5-3 Tage1-4 h
Participantsdifferent
3-121-3 maintaining, briefing for everyone5-153-8
Formatdifferent
WorkshopAsyncWorkshopWorkshop
Outputdifferent
Knowledge Map, Critical Knowledge Areas, Transfer PlanRAID Log, Status Report SourceRich Picture, Root Definitions, Conceptual Models, Change AgendaChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
KnowledgeMappingRisk
RiskTrackingStakeholdersGovernance
Soft systemsComplexitySensemakingSystems thinking
RiskDecisionSensemaking
Add more methods