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 for Communication Plan
Delivery
Communication Plan
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Purposedifferent
When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost.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.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
45-90 min60–90 min20-40 min initial, dann laufend30 min Setup, dann laufend
Participantsdifferent
2-62-83-151-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Communication Plan, Channel Matrix, Message CadenceStakeholder Map, Engagement Plan, Risk NotesROAM Board, Owner ListRAID Log, Status Report Source
Tagsno overlap
CommunicationStakeholdersDeliveryPlanning
StakeholdersAlignmentFacilitationChange
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
Add more methods