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 Force Field Analysis working structure.
Decision Making
Force Field Analysis
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.
Complexitysame
LowLowLow
Timedifferent
20-40 min initial, dann laufend60–90 min45-90 min
Participantsdifferent
3-152-83-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop
Outputdifferent
ROAM Board, Owner ListStakeholder Map, Engagement Plan, Risk NotesForce Field Map, Change Levers, Risk Notes
Tagsno overlap
RiskAgileTrackingAlignment
StakeholdersAlignmentFacilitationChange
ChangeDecisionStrategy
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid