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 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
Paper illustration for DACI
Decision Making
DACI
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 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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.
Complexitydifferent
LowLowHighLow
Timedifferent
30 min Setup, dann laufend20-40 min initial, dann laufend1-4 h30-60 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-153-82-10
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RAID Log, Status Report SourceROAM Board, Owner ListChallenge Findings, Risk Register, Mitigation PlanDACI Matrix, Decision Owner, Decision Log
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
RiskDecisionSensemaking
DecisionRolesGovernanceAlignment
Add more methods