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 Alignment Mapping | ![]() Agile 4Ls Retrospective | ![]() Product Strategy KPI Tree | ![]() Facilitation Expectation Mapping |
|---|---|---|---|---|
Purposedifferent | 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 metrics across the organization drift apart, it arranges drivers and effects under one shared logic. It connects customer value, product logic, and decision priorities. The result is captured as a KPI tree and owner list. | 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 | Medium | Low | Medium | Low |
Timedifferent | 1-2 h | 45–75 min | 90-180 min initial, dann laufend | 45-90 min |
Participantsdifferent | 4-12 | Team members involved | 3-8 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Alignment Map, Open Issues, Decision Questions | 4Ls Board, Learning Themes, Improvement Actions | KPI Tree, Owner List | Expectation Map, Alignment Notes, Agreements |
Tagsno overlap | AlignmentStakeholdersStrategyFacilitation | RetrospectiveLearningReflectionTeam | MetricsStrategyAlignmentMeasurement | AlignmentStakeholdersTeam |



