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 for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Expectation Mapping.
Facilitation
Expectation Mapping
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 dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.When roles, interfaces, or projects fail because of differing expectations, Expectation Mapping surfaces these differences. It shows what each side takes for granted and where the pictures diverge.
Complexitydifferent
LowLowMediumLow
Timedifferent
60–90 min45–75 min15-60 min je Zyklus45-90 min
Participantsdifferent
2-8Team members involved1-83-12
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
Stakeholder Map, Engagement Plan, Risk Notes4Ls Board, Learning Themes, Improvement ActionsSituation Assessment, Decision Loop, Action UpdatesExpectation Map, Alignment Notes, Agreements
Tagsno overlap
StakeholdersAlignmentFacilitationChange
RetrospectiveLearningReflectionTeam
DecisionChangeLearningStrategy
AlignmentStakeholdersTeam
Add more methods