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 Start Stop Continue |  Operations After-Action Review |  Facilitation Responsibility Poker |
|---|---|---|---|
Purposedifferent | When a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. | 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. |
Complexitysame | Low | Low | Low |
Timedifferent | 30-60 min | 20-45 min | 45-90 min |
Participantsdifferent | 3-12 | 3-12 | 3-10 |
Formatdifferent | Workshop | Workshop + async | Workshop |
Outputdifferent | Start Stop Continue Board, Improvement Actions | Lessons learned, Action items, Event summary | Responsibility Map, Role Agreements, Open Questions |
Tagsno overlap | RetrospectiveImprovementTeamReflection | LearningOperationsImprovement | RolesResponsibilityTeamFacilitation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
