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 Argument Mapping
Decision Making
Argument Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
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 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.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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 laufend1-3 h20-40 min initial, dann laufend1-4 h
Participantsdifferent
1-3 maintaining, briefing for everyone1-83-153-8
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceArgument Map, Evidence Gaps, Decision RationaleROAM Board, Owner ListChallenge Findings, Risk Register, Mitigation Plan
Tagsno overlap
RiskTrackingStakeholdersGovernance
SensemakingDecisionRationale
RiskAgileTrackingAlignment
RiskDecisionSensemaking
Add more methods