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
Scenario Planning method illustration showing its working structure
Business Strategy
Scenario Planning
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Purposedifferent
Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path.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 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
HighLowLowMedium
Timedifferent
0.5-2 Tage30 min Setup, dann laufend60–90 min2-4 h
Participantsdifferent
4-121-3 maintaining, briefing for everyone2-83-12
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Scenario Set, Strategic Implications, Robust OptionsRAID Log, Status Report SourceStakeholder Map, Engagement Plan, Risk Notes7S Assessment, Alignment Gaps, Change Actions
Tagsno overlap
StrategyUncertaintyPlanning
RiskTrackingStakeholdersGovernance
StakeholdersAlignmentFacilitationChange
OrganizationStrategyAlignmentChange
Add more methods