View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Decision Making Red Teaming | ![]() Agile Starfish Retrospective | ![]() Agile 4Ls Retrospective |
|---|---|---|---|
Purposedifferent | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. | When improvement options need to be sorted more finely than just start and stop, it brings observations into clear kinds of action. This makes visible what should be done more, less, newly, or continued. | 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. |
Complexitydifferent | High | Low | Low |
Timedifferent | 1-4 h | 45-90 min | 45–75 min |
Participantsdifferent | 3-8 | 4-12 | Team members involved |
Formatsame | Workshop | Workshop | Workshop |
Outputdifferent | Challenge Findings, Risk Register, Mitigation Plan | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RiskDecisionSensemaking | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






