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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
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.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
20-40 min initial, dann laufend1-3 h60–90 min30 min Setup, dann laufend
Participantsdifferent
3-152-82-81-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
ROAM Board, Owner ListGap Matrix, Action Plan, Risk NotesStakeholder Map, Engagement Plan, Risk NotesRAID Log, Status Report Source
Tagsno overlap
RiskAgileTrackingAlignment
StrategyAnalysisPlanning
StakeholdersAlignmentFacilitationChange
RiskTrackingStakeholdersGovernance
Add more methods