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 of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
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 organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.
Complexitydifferent
LowLowHighMedium
Timedifferent
30 min Setup, dann laufend20-40 min initial, dann laufend1-4 h90-180 min
Participantsdifferent
1-3 maintaining, briefing for everyone3-153-84-12
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
RAID Log, Status Report SourceROAM Board, Owner ListChallenge Findings, Risk Register, Mitigation PlanDecision Rights Matrix, Agreement
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
RiskDecisionSensemaking
DecisionGovernanceAlignmentResponsibility
Add more methods