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 8D Problem Solving |  Agile Start Stop Continue |  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. | For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly. | 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. | 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 | Low | High | Low | Low |
Timedifferent | 45-90 min | 1-6 Wochen | 30-60 min | 45–75 min |
Participantsdifferent | 3-10 | 4-10 | 3-12 | Team members involved |
Formatdifferent | Workshop | Workshop + async | Workshop | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | 8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan | Start Stop Continue Board, Improvement Actions | 4Ls Board, Learning Themes, Improvement Actions |
Tagsno overlap | RolesResponsibilityTeamFacilitation | QualityProblem solvingRoot cause | RetrospectiveImprovementTeamReflection | RetrospectiveLearningReflectionTeam |