View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Facilitation Responsibility Poker |  Operations Accountability Ladder |  Agile Starfish Retrospective |  Agile 4Ls Retrospective |
|---|---|---|---|---|
Purposedifferent | When it stays unclear who carries responsibility and who only contributes, Responsibility Poker makes the distribution of responsibility explicit. It sharpens the boundaries between weighing in, deciding, and bearing consequences. | With defensive reactions to problems, the method shifts the view from justification to ownership. It makes visible which reaction stage a person or team is currently stuck on. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 20-45 min | 45-90 min | 45–75 min |
Participantsdifferent | 3-10 | 1-8 | 4-12 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Ownership Reflection, Action Commitment, Coaching Notes | Starfish Board, Practice Changes, Experiments | 4Ls Board, Learning Themes, Improvement Actions |
Tags1 shared | RolesResponsibilityTeamFacilitation | ResponsibilityLeadershipTeam | RetrospectiveImprovementExperimentsTeam | RetrospectiveLearningReflectionTeam |