View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile 4Ls Retrospective |  Team Design Team API |  Facilitation Stakeholder Mapping |
|---|---|---|---|
Purposedifferent | 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 expectations between teams stay fuzzy, it describes how a team can be reached, used, and held accountable. It clarifies responsibility, interaction, and load between teams. The result is captured as a Team API document. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 45–75 min | Half day initial, dann laufend | 60–90 min |
Participantsdifferent | Team members involved | Ein Team plus Stakeholder | 2-8 |
Formatdifferent | Workshop | Workshop + async | Workshop + async |
Outputdifferent | 4Ls Board, Learning Themes, Improvement Actions | Team API Document | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | RetrospectiveLearningReflectionTeam | TeamAlignmentCommunicationService | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
