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 of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Purposedifferent
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.When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures.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.
Complexitydifferent
LowMediumLowMedium
Timedifferent
30 min Setup, dann laufend45-90 min60–90 min2-4 h
Participantsdifferent
1-3 maintaining, briefing for everyone3-82-83-12
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceImpact Map, Outcome Hypotheses, Delivery OptionsStakeholder Map, Engagement Plan, Risk Notes7S Assessment, Alignment Gaps, Change Actions
Tagsno overlap
RiskTrackingStakeholdersGovernance
OutcomesStrategyBehaviorPlanning
StakeholdersAlignmentFacilitationChange
OrganizationStrategyAlignmentChange
Add more methods