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
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of the Consensus Workshop working structure.
Facilitation
Consensus Workshop
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.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 a group needs a solid decision without outvoting individual factions, a Consensus Workshop creates a negotiable common ground. It makes agreement, reservations, and open tensions discussable at the same time.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
20-40 min initial, dann laufend60–90 min1-3 h30 min Setup, dann laufend
Participantsdifferent
3-152-85-301-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopAsync
Outputdifferent
ROAM Board, Owner ListStakeholder Map, Engagement Plan, Risk NotesConsensus Clusters, Theme Titles, Priority AreasRAID Log, Status Report Source
Tagsno overlap
RiskAgileTrackingAlignment
StakeholdersAlignmentFacilitationChange
FacilitationConsensusWorkshopAlignment
RiskTrackingStakeholdersGovernance
Add more methods