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 |  Team Design Team Topologies Interaction Modes |  Facilitation Team Charter |
|---|---|---|---|---|
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 several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements. | When a team is starting fresh or working past each other, Team Charter clarifies the shared working basis. It visibly sets out how collaboration, decision paths, and mutual conduct should work day to day. |
Complexitydifferent | Low | Low | Medium | Medium |
Timedifferent | 45-90 min | 45–75 min | Half day | 2-4 h |
Participantsdifferent | 3-12 | Team members involved | Team-Leads plus Architecture | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Expectation Map, Alignment Notes, Agreements | 4Ls Board, Learning Themes, Improvement Actions | Interaction Heat Map, Agreements per Pair | Team Charter, Working Norms, Role Notes |
Tags1 shared | AlignmentStakeholdersTeam | RetrospectiveLearningReflectionTeam | TeamAlignmentCollaborationOrganization | TeamAlignmentCollaboration |