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 illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
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 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.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.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.
Complexitydifferent
LowMediumLowLow
Timedifferent
60–90 min2-4 h20-40 min initial, dann laufend30 min Setup, dann laufend
Participantsdifferent
2-83-123-151-3 maintaining, briefing for everyone
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Stakeholder Map, Engagement Plan, Risk Notes7S Assessment, Alignment Gaps, Change ActionsROAM Board, Owner ListRAID Log, Status Report Source
Tagsno overlap
StakeholdersAlignmentFacilitationChange
OrganizationStrategyAlignmentChange
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
Add more methods