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
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 Expectation Mapping.
Facilitation
Expectation Mapping
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.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.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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitydifferent
LowLowLowMedium
Timedifferent
45–75 min45-90 min60–90 min1-2 h
Participantsdifferent
Team members involved3-122-84-12
Formatdifferent
WorkshopWorkshopWorkshop + asyncWorkshop
Outputdifferent
4Ls Board, Learning Themes, Improvement ActionsExpectation Map, Alignment Notes, AgreementsStakeholder Map, Engagement Plan, Risk NotesAlignment Map, Open Issues, Decision Questions
Tagsno overlap
RetrospectiveLearningReflectionTeam
AlignmentStakeholdersTeam
StakeholdersAlignmentFacilitationChange
AlignmentStakeholdersStrategyFacilitation
Add more methods