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 board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
A hypothetical failure makes concrete risks, signals, and fitting mitigations visible.
Decision Making
Pre-Mortem
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
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.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.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.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.
Complexitysame
LowLowLowLow
Timedifferent
20-40 min initial, dann laufend20–45 min60–90 min30 min Setup, dann laufend
Participantsdifferent
3-15Small cross-functional group2-81-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
ROAM Board, Owner ListRisk list, Mitigation plan, Assumption logStakeholder Map, Engagement Plan, Risk NotesRAID Log, Status Report Source
Tagsno overlap
RiskAgileTrackingAlignment
RiskDecisionFailurePlanning
StakeholdersAlignmentFacilitationChange
RiskTrackingStakeholdersGovernance
Add more methods