View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Futures Wheel | ![]() Agile 4Ls Retrospective | ![]() Agile Sprint Retrospective | ![]() Agile Mad Sad Glad |
|---|---|---|---|---|
Purposedifferent | The Futures Wheel helps explore the consequences of a decision, a trend, or a strategic move in a structured way. It makes visible which first, second, and third-order effects could arise from an event. | 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 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 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 | Medium | Low | Low | Low |
Timedifferent | 60-120 min | 45–75 min | Up to 3 hours for a one-month Sprint; shorter Sprints are usually shorter | 30-60 min |
Participantsdifferent | 3-10 | Team members involved | Scrum Team | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Futures Wheel, Consequence Chains, Strategic Signals | 4Ls Board, Learning Themes, Improvement Actions | Improvement actions, Team agreements | Emotion Board, Themes, Action Items |
Tagsno overlap | ForesightSystems thinkingSignals | RetrospectiveLearningReflectionTeam | RetrospectiveImprovementLearning | RetrospectiveTeamReflection |



