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
A structured reflection surfaces what was liked, learned, lacked, and longed for. It is a conversation format and does not validate actions automatically.
Agile
4Ls Retrospective
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
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.When a sprint should not only be assessed but also learned from, it captures experience in clear learning categories. It records what worked, what's missing, and what should run differently next time.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
60–90 min45–75 min45-90 min
Participantsdifferent
2-8Team members involved3-12
Formatdifferent
Workshop + asyncWorkshopWorkshop
Outputdifferent
Stakeholder Map, Engagement Plan, Risk Notes4Ls Board, Learning Themes, Improvement ActionsForce Field Map, Change Levers, Risk Notes
Tagsno overlap
StakeholdersAlignmentFacilitationChange
RetrospectiveLearningReflectionTeam
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 for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping