View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Execution Loop |  Agile Sprint Retrospective |  Agile 4Ls Retrospective |  Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | When a sprint is over and friction shouldn't simply be carried forward, it opens the view onto collaboration and patterns. It creates space to see causes and changes together. | 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 a team's or workshop's mood needs to become readable, it structures emotional signals with little setup. It makes strain, relief, and sources of energy tangible. |
Complexitydifferent | High | Low | Low | Low |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 45–75 min | 30-60 min |
Participantsdifferent | 5-12 | Scrum Team | Team members involved | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Improvement actions, Team agreements | 4Ls Board, Learning Themes, Improvement Actions | Emotion Board, Themes, Action Items |
Tagsno overlap | ExecutionCadenceLearningGovernance | RetrospectiveImprovementLearning | RetrospectiveLearningReflectionTeam | RetrospectiveTeamReflection |