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 |  Agile Example Mapping |  Facilitation Delegation Poker |  Facilitation Lean Coffee |
|---|---|---|---|---|
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. | When a story carries business rules and exceptions, it brings clarity before implementation. It makes examples, open questions, and boundaries visible enough that the logic becomes jointly sound. | 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 group without a fixed agenda needs to get into useful conversations quickly, Lean Coffee structures the start around interests rather than a presentation. The group itself negotiates which topics get time first and which wait. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 45-90 min | 30-60 min | 45-90 min | 30-90 min |
Participantsdifferent | 3-10 | 3-7 | 3-10 | 3-20 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Responsibility Map, Role Agreements, Open Questions | Example Map, Acceptance Criteria, Open Questions | Delegation Board, Decision Boundaries, Role Agreements | Prioritized Topics, Discussion Notes, Action Items |
Tagsno overlap | RolesResponsibilityTeamFacilitation | Behavior-Driven DevelopmentRequirementsExamplesRefinement | AutonomyRolesTeam | FacilitationAutonomyDialogue |