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 | ![]() Agile 4Ls Retrospective | ![]() Agile ROAM Board | ![]() Facilitation Alignment 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 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 work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | 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 | Low | Low | Low | Medium |
Timedifferent | 45-90 min | 45–75 min | 20-40 min initial, dann laufend | 1-2 h |
Participantsdifferent | 3-12 | Team members involved | 3-15 | 4-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | 4Ls Board, Learning Themes, Improvement Actions | ROAM Board, Owner List | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | AlignmentStakeholdersTeam | RetrospectiveLearningReflectionTeam | RiskAgileTrackingAlignment | AlignmentStakeholdersStrategyFacilitation |



