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
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping
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
Purposedifferent
In early initiatives with many uncertainties, planning quickly turns too optimistic. A pre-mortem makes the expected failure visible in advance and sharpens the view of causes, gaps, and countermeasures.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.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
20–45 min90-180 min30 min Setup, dann laufend20-40 min initial, dann laufend
Participantsdifferent
Small cross-functional group4-121-3 maintaining, briefing for everyone3-15
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Risk list, Mitigation plan, Assumption logDecision Rights Matrix, AgreementRAID Log, Status Report SourceROAM Board, Owner List
Tagsno overlap
RiskDecisionFailurePlanning
DecisionGovernanceAlignmentResponsibility
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
Add more methods