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 RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Red Teaming method illustration showing its working structure
Decision Making
Red Teaming
Purposedifferent
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 problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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
LowMediumLowHigh
Timedifferent
30 min Setup, dann laufend60-180 min15-45 min1-4 h
Participantsdifferent
1-3 maintaining, briefing for everyone4-201-33-8
Formatdifferent
AsyncWorkshopAsyncWorkshop
Outputdifferent
RAID Log, Status Report SourceCynefin Map, Domain-specific Actions, Sensemaking NotesADR File, Decision Log, RationaleChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
RiskTrackingStakeholdersGovernance
ComplexitySensemakingDecision
ArchitectureRationaleDocumentationGovernance
RiskDecisionSensemaking
Add more methods