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 Delegation Poker |  Agile Mad Sad Glad |  Operations After-Action Review |  Agile Start Stop Continue |
|---|---|---|---|---|
Purposedifferent | When decisions get stuck between leadership and team, Delegation Poker clarifies the desired scope of autonomy. It shows how much decision-making latitude a role should actually get in practice. | 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. | 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 a team wants to deliberately adjust its working behavior, it makes habits visible and assessable. It focuses on concrete changes instead of diffuse mood. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30-60 min | 20-45 min | 30-60 min |
Participantsdifferent | 3-10 | 3-10 | 3-12 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop |
Outputdifferent | Delegation Board, Decision Boundaries, Role Agreements | Emotion Board, Themes, Action Items | Lessons learned, Action items, Event summary | Start Stop Continue Board, Improvement Actions |
Tagsno overlap | AutonomyRolesTeam | RetrospectiveTeamReflection | LearningOperationsImprovement | RetrospectiveImprovementTeamReflection |