View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Team Design Team Topologies Interaction Modes |  Agile 4Ls Retrospective |  Facilitation Expectation Mapping |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | 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 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | Half day | 45–75 min | 45-90 min | 30-60 min |
Participantsdifferent | Team-Leads plus Architecture | Team members involved | 3-12 | 3-12 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Interaction Heat Map, Agreements per Pair | 4Ls Board, Learning Themes, Improvement Actions | Expectation Map, Alignment Notes, Agreements | Start Stop Continue Board, Improvement Actions |
Tags1 shared | TeamAlignmentCollaborationOrganization | RetrospectiveLearningReflectionTeam | AlignmentStakeholdersTeam | RetrospectiveImprovementTeamReflection |