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
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
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.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.When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.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
LowLowMediumLow
Timedifferent
60–90 min20-40 min initial, dann laufend1-2 h30 min Setup, dann laufend
Participantsdifferent
2-83-154-121-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
Stakeholder Map, Engagement Plan, Risk NotesROAM Board, Owner ListAlignment Map, Open Issues, Decision QuestionsRAID Log, Status Report Source
Tagsno overlap
StakeholdersAlignmentFacilitationChange
RiskAgileTrackingAlignment
AlignmentStakeholdersStrategyFacilitation
RiskTrackingStakeholdersGovernance
Add more methods