View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Expectation Mapping |  Facilitation Alignment Mapping |  Agile 4Ls Retrospective |  Facilitation Stakeholder Mapping |
|---|---|---|---|---|
Purposedifferent | 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 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. | 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 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. |
Complexitydifferent | Low | Medium | Low | Low |
Timedifferent | 45-90 min | 1-2 h | 45–75 min | 60–90 min |
Participantsdifferent | 3-12 | 4-12 | Team members involved | 2-8 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | Alignment Map, Open Issues, Decision Questions | 4Ls Board, Learning Themes, Improvement Actions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | AlignmentStakeholdersTeam | AlignmentStakeholdersStrategyFacilitation | RetrospectiveLearningReflectionTeam | StakeholdersAlignmentFacilitationChange |